execute_booking_cancellation

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses meaningful behavior: it rechecks the reservation, sends at most one cancellation request, reconciles with fresh reads, and never retries automatically. It also transparently notes that only one standard cancellation branch was observed live and that late/other branches remain unverified, which is valuable cautionary context.

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 front-loaded with the core purpose and then adds only high-value safety and behavioral details. Each sentence earns its place, including the consent requirement, no-retry rule, and live-verification caveat, without padding or redundancy.

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 destructive, non-idempotent tool with an output schema, the description covers the essential operational context: consent proof, rechecking, single request, reconciliation, and the unresolved late-credit-loss branch. The presence of an output schema means return values need not be described, and nothing critical for correct invocation is missing.

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?

With 0% schema description coverage, the description must compensate, and it does add meaning for confirmed (must be true and backed by explicit consent) and actionReference (a reference alone does not prove consent). However, it leaves gymId unexplained and does not clarify the actionReference format beyond what the schema pattern already provides, so the compensation is incomplete.

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 opens with a specific verb and resource, 'Cancel one exact prepared booking,' which clearly states the tool's function. It also distinguishes itself from siblings like execute_late_booking_cancellation by referring to a 'standard cancellation request' and an exact prepared booking, so an agent can tell it apart without opening schemas.

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 explicit preconditions: the MCP client must show the preview and obtain explicit account-holder confirmation before calling with confirmed: true, and it warns never to retry automatically. It does not explicitly name alternatives or state when to prefer execute_late_booking_cancellation, but the context strongly implies the standard-cancellation path.

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