get_payment

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'fetch details', indicating a read operation, but fails to mention potential errors, rate limits, required permissions, or the structure of returned details. This is minimal transparency for a simple 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?

Single sentence, no wasted words, front-loaded with the core action. Perfectly concise for the tool's simplicity.

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 one required parameter, no output schema, and no nested objects, the description is adequate but could be more complete. It doesn't clarify what 'details' includes (e.g., status, amount, date) or how it differs from 'get_payment_analytics'. Lacks precautionary context like error handling.

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%, with the parameter 'payment_id' described as 'Payment ID, e.g. pay_xxxxx', adding a format example beyond the schema type. The description itself does not repeat parameter info, but the example adds value. Baseline 3 raised to 4 for the example.

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 'Fetch details of a specific payment by ID' clearly states the action (fetch), resource (payment), and scope (by ID). It distinguishes from siblings like 'list_payments' (list vs single) and 'get_payment_analytics' (analytics vs details).

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 on when to use this tool versus alternatives (e.g., list_payments for multiple payments, get_payment_analytics for aggregated data). Usage is implied by the description but not explicitly stated with when/when-not criteria.

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