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 contributes the non-obvious Admin-role authorization requirement, which is genuine added context. It says nothing about how the period is bounded when start/end are omitted, or about result size/aggregation, leaving behavioral gaps.

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 with the permission constraint attached to the tool name, no filler. It is arguably terse to the point of under-specification, but every clause earns its place.

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 reporting tool with six optional parameters, no required fields, and no output schema, an agent still cannot tell what happens with an unbounded or empty period, nor what shape the report returns. The Admin prerequisite is present, but the 'all parameters optional' behavior is left unexplained.

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 six parameters already carry their own docs including date formats and id semantics. The description adds no parameter-level meaning such as whether filters combine (AND) or how user_id/matter_id narrow the collected-payments figures, 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?

Names a specific resource and scope: 'payments the firm collected in a period,' which is a clear verb+resource statement. It is distinguishable from lawcus_report_revenue or lawcus_report_invoice_history by the 'collected payments' framing, though the description never explicitly contrasts with those siblings.

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 '(needs the Admin role)' clause gives a real prerequisite for when the call will succeed. However, nothing tells an agent when to pick this report over lawcus_report_revenue, lawcus_report_invoice_history, or lawcus_report_accounts_receivable — the closest alternatives in the sibling list.

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