get_aged_receivables

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

No annotations provided; description only states it generates a report. Lacks disclosure on read-only nature, permissions needed, or whether data is a snapshot. No mention of limitations like pagination or date ranges.

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?

Single sentence with no unnecessary words. Front-loaded with the purpose.

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?

No output schema; description lacks details on return format, pagination, or limitations. For a report with multiple parameters, additional context would improve usability.

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 descriptions cover all parameters (report_date, customer, etc.) but tool description adds no extra meaning. With 50% schema coverage baseline, the description does not compensate.

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 clearly states the tool generates an Aged Receivables report from QuickBooks Online, specifying the resource (A/R Aging) and verb (Generate). It distinguishes from siblings like get_aged_payables and get_invoice.

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 explicit guidance on when to use this tool versus alternatives like get_customer_balance or get_customer_sales. Usage is implied but not stated when not to use.

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