xero_list_prepayments

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

Annotations are absent, and the description only notes routing and scope. It does not disclose important behavioral traits like read-only nature, data access limitations, or return format, forcing the agent to infer from the tool name.

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 and structured with a heading, routing line, and parameter block. However, it omits critical information, making it under-specified for effective tool usage.

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 complexity and many sibling tools (e.g., xero_list_accounts, xero_list_invoices), the description lacks context such as what prepayments are, filtering capabilities, or output details. The agent cannot determine how to use this tool effectively.

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 sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which adds no meaningful semantics beyond the schema. With 0% schema description coverage, the tool fails to explain expected JSON structure or keys.

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 explicitly states it is a 'list_prepayments' operation, clearly indicating the verb (list) and resource (prepayments). However, it does not differentiate from other list tools in Xero or define what a prepayment is, leaving ambiguity.

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_invoices or other list operations. There is no mention of prerequisites, filters, or scenarios where this tool is appropriate.

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