xero_list_payments

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

With no annotations, the description must disclose behavior. It only mentions routing (JWT, tenant, scope) but not whether the operation is read-only, returns paginated results, or any other behavioral traits. The description is insufficient for an agent to assess safety or 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 concise and front-loaded with the core purpose. However, it sacrifices informational content for brevity, leaving out details that would fit in the same space.

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 a simple list operation with an output schema, the description should at least hint at parameter structure or pagination. It does not, leaving an agent without enough context to invoke the tool correctly without external knowledge of the Xero API.

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 schema has one parameter 'arguments' (JSON string) with 0% schema coverage. The description merely repeats 'JSON string of arguments for the connector operation,' adding no semantic meaning. It does not explain required keys, optional filters, or formatting.

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 states it is a Xero connector operation to list payments, which is clear from the name and text. However, it does not elaborate on the scope (e.g., all payments, filtered) or differentiate from other list tools in the Xero family beyond the 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?

No guidance is provided on when to use this tool versus alternatives like xero_create_payment or xero_list_invoices. There are no prerequisites, context hints, or exclusions mentioned.

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