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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value by disclosing that the reply carries trust/retainer balances and opened/closed counts, and that results are paged with skip/take. It stops short of describing default page size or sort-order behavior, which the schema covers instead.

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?

Three tight sentences with no filler: what it returns first, filters second, paging and reply metadata last. Every clause carries information an agent can act on.

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 no output schema, the description usefully sketches the return payload (balances, counts) and paging contract, which is enough for a read-only list tool. Only sorting behavior and the interplay of top-level shortcuts with the advanced filters array go unaddressed, and the schema carries those.

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 75%, so most parameters are already documented, and the description only restates the obvious filter axes. It adds no meaning for sort_by, sort_order, responsible_attorney_id or the advanced filters array beyond what the schema provides, so it sits at the baseline.

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 verb and resource (list matters/cases) plus the notable fields each record carries (status, client, billing type, trust and retainer balances), which distinguishes it from a bare listing. It does not explicitly contrast with lawcus_get_matter or lawcus_search, so sibling differentiation is left implicit.

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 filter dimensions (status, name, number, client, dates) and paging behavior imply when to reach for this tool, but there is no explicit when-not guidance or a named alternative such as lawcus_get_matter for single-record retrieval. Usage is inferable rather than stated.

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