xero_payments

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

Without annotations, the description should disclose safety and reliability aspects. It only says 'Get payments' but doesn't indicate if the operation is read-only, if it returns all payments or requires filters, or any potential 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 a single sentence and concise, but it is too brief for a tool with multiple parameters. It lacks structure and does not earn its place by adding value beyond the name.

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 five parameters, no output schema, and no annotations, the description is severely incomplete. The agent has no information about response format, filtering capabilities, or required authentication, making the tool difficult to use correctly.

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 0% schema description coverage, the description must compensate but does not. The five parameters (status, date_from, date_to, access_token, tenant_id) are unexplained, leaving the agent unable to use them 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 retrieves payments from Xero, which is a specific verb and resource. However, it does not differentiate from sibling tools like xero_invoices or xero_bank_transactions, both of which could also retrieve payment-related data.

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. There is no mention of prerequisites such as authentication tokens or tenant IDs, which are required parameters.

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