xero_aged_payable_report

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

No annotations are provided, so the description must disclose behavioral traits. It mentions routing and authentication scope but does not state whether the tool is read-only, destructive, or any rate limits. The name suggests it fetches a report, but this is not explicit, leaving agents unaware of side effects.

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?

The description is short with two sentences, but the first sentence restates the tool name and the second provides route context. It avoids fluff, yet the lack of parameter detail makes it feel insufficient. It is concise but incomplete.

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?

Given the tool's complexity (a report with unknown arguments) and the absence of parameter description, the description is incomplete. An output schema exists but does not excuse the lack of input guidance. The agent cannot determine how to use the tool effectively from this description alone.

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%, so the description must compensate. It only states 'arguments: JSON string of arguments for the connector operation,' which adds minimal semantics. It does not explain the expected structure, keys, or formats, forcing the agent to guess or rely on external docs.

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 the tool as 'aged_payable_report' and specifies it is a Xero connector operation. This clearly indicates the resource (aged payable report) and verb (report/retrieve), distinguishing it from sibling tools like xero_aged_receivable_report and quickbooks_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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context for use, or situations to avoid. For instance, it does not differentiate from the similar xero_aged_receivable_report tool.

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