booking_cancel_reservation

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

No annotations provided, so description carries full burden. It discloses irreversible cancellation with confirm=true, the multi-step flow, and that without confirm=true it returns a warning and never opens a browser. No contradictions.

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?

Two sentences with zero waste. The critical purpose is front-loaded, followed by essential usage notes. Every sentence earns its place.

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 no output schema, description adequately covers behavior for both confirm states and the multi-step flow. It does not detail post-cancellation results (e.g., refund), but main requirements are met.

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 coverage is 100%, baseline 3. Description adds context: explains confirm's irreversible effect and reservationId format (including multi-booking trips and URL acceptance), which adds value beyond schema.

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 states the tool cancels an existing reservation, using specific verb 'cancel' and resource 'reservation'. It distinguishes from siblings like booking_book (make reservation) and booking_get_reservations (retrieve reservations).

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 provides clear guidance: use confirm=true only with explicit user confirmation; without confirm, it's a no-op warning. It explains the multi-step flow, but does not explicitly compare with alternatives like modifications.

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