xero_list_prepayments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description reinforces that with 'effect must be read; Spring verifies it.' It adds a routing/authority constraint and clarifies approval_ref is for resuming a write, but does not add details like pagination or rate limits. No contradiction with annotations.

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 compact, front-loads the operation identity, and uses a clean Args list. Every line provides some information, though the Args list is boilerplate-like. No redundant content, appropriate size for seven 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?

With an output schema present, return-value documentation isn't needed, and annotations cover the safety profile. However, the description leaves a key gap: the contents of the `arguments` JSON string are unspecified, and there is no guidance distinguishing this list operation from the dozen other Xero list siblings. The routing note and parameter hints are useful but not fully complete for correct invocation.

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's Args block is the only parameter documentation. It gives one-line meanings for each parameter (e.g., project_id is Authenticated Project UUID). However, the most important parameter, `arguments`, is only described as 'JSON string of arguments for the connector operation,' which is tautological and doesn't tell the caller what keys the Xero operation accepts.

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 specific Xero connector operation `list_prepayments` and its platform tool ID, making the resource and verb clear from the name. It does not, however, explain what a prepayment is or what information the call returns, and it doesn't distinguish itself from the many sibling xero_list_* operations beyond the resource name.

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?

The only usage-related sentence is 'Routes only through the exact project/account governed connector authority,' which is a routing constraint, not guidance on when to call this tool. There is no mention of when to prefer it over xero_list_overpayments, xero_list_payments, or other list tools, and no when-not-to-use conditions.

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