xero_payments_get

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

Description indicates a read operation ('Get detailed information'), but with no annotations, it fails to disclose any behavioral traits such as auth requirements, rate limits, or side effects beyond the basic retrieval.

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?

Single sentence of 12 words, efficient and front-loaded. No unnecessary information.

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?

For a simple get-by-ID tool with one parameter and no output schema, the description sufficiently conveys the purpose and return value ('detailed information'). Completeness is adequate, though could specify example fields.

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 100% (paymentId described as 'The unique payment ID (UUID)'), and description adds no additional parameter meaning beyond restating the schema. Baseline score of 3 applies.

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?

Description clearly states 'Get detailed information about a specific payment by its ID.' Uses specific verb and resource, and distinguishes from sibling tools like xero_payments_list (list all) and xero_payments_create (create).

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?

Implies usage for retrieving a single payment by ID, but provides no explicit guidance on when to use this over alternatives like listing all payments.

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