cancel_payment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates cancellation is conditional, but it does not disclose whether the operation is destructive, whether it can be reversed, what errors occur if the payment is not cancellable, or any side effects. This is a significant gap for a mutation 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?

The description is a single short sentence with no wasted words. It is front-loaded with the action and resource, though it could earn a higher score by adding more useful detail without becoming verbose.

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 mutation tool with no annotations, no output schema, and a single undocumented parameter, the description is too thin. It does not explain preconditions (how to know a payment is cancellable), failure behavior, or return value. An agent would likely need to guess or call the tool blindly.

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 0%, and the description does not explain the payment_id parameter beyond its name. The schema only says it is a string, so the description adds no meaning about format, required context, or how to obtain a valid payment_id. The description fails to compensate for the lack of schema documentation.

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 a specific verb ('Cancel') and resource ('a payment'), and adds a scope condition ('only while still cancellable'). It is clear what the tool does, though it does not explicitly distinguish it from siblings like get_payment or list_payments beyond the obvious action.

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 phrase 'only while still cancellable' implies a timing condition for use, but it does not explain how to determine cancellability, what happens if the payment is not cancellable, or when to prefer this over alternatives. Some guidance is present, but it is incomplete.

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