xero_list_overpayments

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

The description mentions routing details and scope requirements, which provides some behavioral context. However, it lacks information on pagination, default behavior, or error handling. Since no annotations exist, the description carries the full burden but addresses it only partially.

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 brief (three sentences) and avoids fluff, but it omits essential usage details. It earns a 3 for not being overly verbose, but the lack of critical information prevents a higher score.

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?

Despite the output schema existing to describe return values, the description fails to explain how to provide input via the 'arguments' parameter. This is a significant gap for a tool with one parameter, making the description incomplete for practical use.

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 single parameter 'arguments' is a JSON string with no description in the schema or the tool description. Schema coverage is 0%, and the description does not clarify what keys or values are expected inside the JSON. This leaves the agent completely in the dark about how to invoke the tool correctly.

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 lists overpayments, but does not differentiate from sibling tools like xero_list_payments or xero_list_credit_notes. The verb 'list' is appropriate and the resource 'overpayments' is specific.

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 such as xero_list_payments or xero_list_credit_notes. There is no context on prerequisites or typical scenarios.

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