get_ar_aging

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

With no annotations provided, the description carries the full behavioral burden, and 'Read-only report' does substitute for the missing readOnlyHint, which is genuinely useful. However, it says nothing about scoping (whole organization vs. filtered), permissions required, or whether results are period-dependent, leaving behavioral gaps the annotations would normally cover.

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 sentence plus a short qualifier, front-loaded with the resource and followed by the bracket detail. Every clause earns its place and there is 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?

For a zero-parameter read-only report with no output schema, the description usefully enumerates the return brackets so the agent knows what it will get back. The only shortfall is the absence of any statement about scoping or time period, which matters for an aging report.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. The bracket list in the description describes output shape rather than parameter meaning, so there is nothing further for the description to add here.

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?

The description names a specific verb ('Get') and resource ('accounts-receivable aging brackets') and enumerates the exact brackets returned, so the agent knows precisely what report this is. It does not explicitly name sibling get_ap_aging as the counterpart, but the 'accounts-receivable' scope makes the distinction self-evident.

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?

Usage is implied by the resource itself — an aging report is fetched when overdue receivables are needed — but there are no explicit when-to-use or when-not conditions and no mention of alternatives such as get_ap_aging or get_trial_balance. No exclusions or prerequisites are given.

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