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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds value beyond that by disclosing the response shape (count/total, aging breakdown, per-entry invoiceId). It does not mention ordering, limits, or freshness, which are relevant for an aging report.

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?

Two sentences, front-loaded with what is returned and followed by the actionable link to sibling tools. Every clause earns its place with no redundancy.

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 parameters and no output schema, the description carries the burden of describing returns, and it does so at a high level (count, total, aging breakdown, invoiceId). It leaves the exact aging bucket boundaries and whether totals are per-currency unstated, a minor gap.

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?

Zero parameters, so there are no semantics to explain and the baseline of 4 applies. The description correctly spends none of its budget on parameter detail.

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 ('Get count/total of open and overdue invoices plus aging breakdown'), scoping it narrower than the generic query_invoices sibling. It never names query_invoices explicitly, so the differentiation is inferred from the 'open and overdue' qualifier 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?

Gives clear downstream guidance: the returned invoiceId feeds send_reminder or mark_invoice_paid. It stops short of stating when to prefer this over query_invoices or how often aging data refreshes, so no explicit exclusions are offered.

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