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

With no annotations, the description carries the full burden; it does add a genuinely useful domain rule ('An invoice with no due date is due when sent') and describes the output grouping. However, it never states that the operation is read-only, whether results are paginated, or what the response shape is beyond the bucket labels.

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 dense sentences with the resource and the bucket taxonomy front-loaded, and the due-date edge case placed last where it belongs. No filler or 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?

The description sketches the return values (bucket columns, per-customer totals), which partly compensates for the absent output schema, but with two undocumented parameters and no read-only or pagination statement, an agent still lacks pieces needed to call it correctly.

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 0%, and the description mentions neither parameter. In particular, the meaning of as_of (the reference date used to compute bucket age) is entirely undocumented, leaving the agent to guess how the aging is anchored.

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 (accounts receivable aging / open invoice balances) and enumerates the exact buckets (current, 1-30, 31-60, 61-90, over 90) plus the per-customer totals, so the agent knows precisely what it produces. It does not distinguish itself from near-siblings such as reports_owed or customers_statement, which keeps it short of a 5.

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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance, even though reports_owed and customers_statement overlap with this tool's territory. The agent must infer the trigger condition from the tool's domain name alone.

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