Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint=true and openWorldHint=true, the description discloses two substantive behavioral facts: the Admin permission requirement and the default row-filtering rule (zero balances hidden unless display_zero is true). It does not describe return shape or whether start/end are optional filters, but for a read-only report the additions are meaningful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the permission constraint and the default-filter behavior front-loaded; no filler, and every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no output schema, and sparse annotations, the description covers permissions and default filtering adequately. It stops short of indicating what the report rows contain or whether start/end are required to produce meaningful output, which would round it out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, and the description covers the one gap: display_zero has no schema description, and the description explains its effect as an override of the default hiding of zero balances. The date-range and id parameters are left to the schema, which documents them well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (client trust / IOLTA balances) produced by a report, which is clearly distinct from the sibling reports (accounts_receivable, matter_balance, revenue, payments_collected). The verb is nominal ("report") rather than a true action verb, and no sibling is explicitly named as an alternative, keeping it just under a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a real precondition — "needs the Admin role" — which is useful and non-obvious. However, it gives no when-to-use guidance relative to the other report tools or the client/matter listing tools, so an agent must infer the selection context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.