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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only the derivation lineage ('from aged receivables v2'), which is genuinely useful context, but says nothing about what constitutes 'overdue', the date semantics, or return shape.

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 efficient sentence that is front-loaded with the action and resource. It is not bloated, though it is terse enough that the missing 'when/how' information is a coverage gap rather than a conciseness win.

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 read-only reporting tool with no output schema, the description is thin: it omits what 'overdue' means, whether the result is a list or summary, and how it differs from the aged-receivables tools it references. Annotations cover safety, but the data semantics are left to inference.

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 dateFrom, dateTo, and companyId are already documented in the schema with types and formats. The description adds no parameter meaning beyond this, so the baseline 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 clear verb ('Get') and resource ('overdue receivables'), which is more specific than the bare name suggests. It also flags the data source ('derived from aged receivables v2'), giving partial differentiation, but it never clarifies how this differs from the sibling get-aged-receivables-v2 or why the name says 'invoices' while the description says 'receivables'.

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?

No when-to-use guidance and no explicit alternatives. The phrase 'derived from aged receivables v2' implies a relationship to that sibling but doesn't tell the agent which one to pick or under what conditions, leaving the choice ambiguous among get-aged-receivables, get-aged-receivables-v2, and get-invoice-pending-summary.

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