quickbooks_aged_payable_report

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as read-only nature, returned data structure, permissions needed, or limitations. Only the basic function is described.

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?

Concise with a short purpose statement followed by a list of arguments. No fluff, but could be more structured with clear separation between purpose and parameters.

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?

Output schema exists, so return values need not be explained. However, lacks explanation of 'aged payables' concept, available columns, and missing behavioral context due to no annotations. Adequate but not rich.

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?

Adds meaning beyond the schema by specifying date format (YYYY-MM-DD) and optional nature of parameters. However, does not explain valid column values or default behavior. Schema coverage is 0%, so description compensates minimally.

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?

Clearly states the verb (Fetch), resource (QuickBooks aged payables report), and purpose (AP aging and vendor cash planning). Distinguishes from sibling tools like quickbooks_aged_receivable_report and xero_aged_payable_report.

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?

Implies usage for AP aging and cash planning but does not explicitly state when to use this tool versus alternatives like balance sheet or cash flow reports. No exclusions or when-not-to-use guidance provided.

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