get_payment

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. However, the description itself adds no behavioral context beyond a generic 'get' – it does not explain what is returned, whether the record is ephemeral, or any additional effects, so it contributes nothing beyond the annotations.

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?

At two words, the description is technically concise but it is under-specified and doesn't earn its place: it just repeats the title. A useful description could add purpose and usage context with minimal length.

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?

Even for a simple single-parameter get-by-id tool, the description is not complete. The schema and annotations cover the parameter and safety, but the description fails to explain the domain meaning of a payment or route the agent to the correct sibling tool, leaving an agent to infer when to use get_payment vs list_payments or get_payout.

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%; the only parameter, payment_id, is already documented as 'Payment UUID'. The description does not add parameter meaning, but the baseline of 3 applies when the schema fully covers parameters.

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 'Get Payment' merely restates the tool's name and title, making it a tautology. It identifies a verb and resource but provides no detail about what a 'payment' means in this domain or how this tool differs from siblings like list_payments or get_payout.

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?

The description gives no guidance on when to use this tool versus alternatives. There is no mention of list_payments for retrieving all payments or get_payout for a related financial entity, and no conditions or exclusions are stated.

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