What is a common mistake with use case boundaries in Clean Architecture?

Creating use cases that mirror database CRUD rather than business intent can produce an anemic application layer. In practice, the value of this concept comes from understanding where it belongs in the architecture, what problem it solves, and what constraints or tradeoffs it introduces.