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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds the useful semantic scope (only unpaid invoices), but says nothing about aging buckets, sorting, or result shape. Adequate but not rich given the annotations already carry the behavioral load.

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?

One sentence plus one trigger-phrase clause; the core purpose is front-loaded and every word 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?

For a parameterless tool with no output schema, the description adequately conveys what comes back (unpaid invoices and days past due). It leaves minor gaps around the aging-bucket structure and its relationship to the duplicate get_ar_aging sibling.

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 baseline a 4 applies. There is no parameter surface for the description to clarify or omit.

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 resource (accounts-receivable aging) and the return content (unpaid invoices with days past due), so the agent knows exactly what it yields. However it never distinguishes itself from the near-identical sibling get_ar_aging, nor from find_invoices, which the description's 'overdue invoices' phrasing overlaps with.

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?

Provides explicit trigger phrases ('AR aging', 'overdue invoices', 'who owes us'), which gives clear context for when to reach for it. It stops short of naming alternatives or exclusions, so there is no guidance on when to prefer get_ar_aging or find_invoices instead.

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