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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuinely useful non-annotation fact — the Admin role requirement. It stops short of disclosing response shape, aggregation granularity, or how the optional filters interact with the aggregate, which matters for a report tool.

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 front-loaded sentence that packs the resource, the permission gate, and the mode switch with no filler. It reads as a terse fragment rather than a full sentence, but every clause carries information.

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?

For a seven-parameter, zero-required report with no output schema, the description is minimally adequate: it says what is summarized and who may call it. It does not say what the report returns, how grouping affects the result, or whether omitting start/end defaults to all time, leaving an agent to infer call behavior.

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 description coverage is 100%, so all seven parameters are documented in the schema (date formats, user/client/practice ids, group_by pattern). The description only touches the trust parameter implicitly and adds nothing about how start/end/group_by scope the report, so the baseline of 3 applies.

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?

States a specific resource (balance summary of all matters) and a scope modifier (optionally trust balances only), so the agent knows this is an aggregated financial report rather than a record fetch. It does not explicitly name which sibling report it substitutes for (e.g. lawcus_report_client_trust or lawcus_report_accounts_receivable), so differentiation is inferred rather than stated.

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?

The Admin-role prerequisite is stated and the 'trust balances only' mode is implied, which gives partial usage context. However, there is no explicit when-to-use guidance versus the other report siblings, and no indication of when the trust mode should be preferred over the full balance summary.

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