xero_list_payments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds some context by stating that routing is restricted to the governed project/account authority and that effect must be read and verified by Spring. However, it does not describe return behavior, pagination, or filtering, and the approval_ref note about resuming a write is irrelevant boilerplate for a read-only tool.

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 and well structured: an identity/routing sentence followed by a clean bullet list of parameters. It wastes little space. The first sentence is somewhat tautological and the approval_ref note is write-oriented boilerplate, but overall the structure is clear and scannable.

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?

Annotations and output schema cover safety and return values, but the definition does not explain the actual functional semantics of list_payments or the expected contents of the `arguments` JSON. Without that, an agent knows this is a governed read operation but not how to invoke the underlying Xero operation correctly. It also provides no differentiation from the many sibling list operations in the environment.

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?

With schema description coverage at 0%, the description does compensate by listing each parameter with a short gloss and correctly marks effect as required and read-only. But the critical `arguments` parameter is only described as 'JSON string of arguments for the connector operation', with no keys, filters, shape, or example. An agent still cannot confidently construct the arguments payload for a Xero list_payments call.

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 opening sentence merely restates the tool name and platform path: 'Xero connector operation `list_payments` (platform tool `xero.list_payments`)'. It never explicitly says that the operation retrieves a list of payments or what a payment is in this context. The verb/resource are only inferable from the name, making this closer to tautology than explanation.

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?

There is no guidance about when to use this tool versus alternative tools, despite a huge sibling list containing other payment-listing tools such as billcom_list_payments and quickbooks_list_payments. The routing note 'Routes only through the exact project/account governed connector authority' is a constraint on invocation, not a usage recommendation. 'Xero connector operation' implies Xero context, but no explicit when/when-not conditions are given.

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