execute_late_booking_cancellation

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

Annotations (destructiveHint:true, idempotentHint:false) are already present, but the description adds crucial context: it requires a UI confirmation step, sends at most one request, reconciles by reading, and explicitly states it does not verify refund or balance. This goes beyond the annotations and tells the agent what side effects to expect.

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?

Every sentence adds value: it front-loads the mandatory confirmation step, then the call condition, then the behavior after the call. It is dense but not verbose, with no filler. The structure logically guides the agent through the required sequence.

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 complex mutation tool with an output schema, the description covers the entire workflow: what to do before calling, what parameters to pass, what the tool does (rechecks, sends once, reconciles), and what it doesn't verify. An agent has all the information needed to invoke it correctly without ambiguity.

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%, so the description carries the burden. It explains the meaning of the two required parameters: actionReference must be the NEW one from the prior call, and confirmedCreditLoss must be true. It does not explain gymId, which is optional, but for the essential parameters it adds useful semantics beyond the schema's raw constraints.

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 defines the tool as the follow-up to a normal cancellation when credit loss is pending. It names the sibling execute_booking_cancellation and specifies the exact condition ('reports pending-credit-loss') that triggers this tool, distinguishing it from other cancellation tools.

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?

Explicitly states the precondition: 'After execute_booking_cancellation reports pending-credit-loss'. It mandates a separate explicit confirmation and instructs to 'Only then call with the NEW actionReference and confirmedCreditLoss: true'. Also prohibits automatic retries, giving clear when-to-use and when-not-to-use guidance.

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