execute_booking_cancellation

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

Annotations already declare destructive, openWorld, and non-idempotent, and the description adds real operational context: reservation recheck, at most one standard request, reconciliation with fresh reads, and a pending late-credit-loss warning with a new reference that must not be retried. This is exactly the behavior an agent needs before an irreversible call.

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?

Front-loaded with the core action, then prerequisites and failure handling, with no filler sentences. Some phrasing is opaque jargon ("standard request", "fresh reads", "publication preference switches") that costs a little clarity.

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 two-parameter destructive action with an output schema, the description covers preconditions, the confirmation gate, retry policy, and the pending-warning outcome. Only the actionReference provenance and the choice among cancellation siblings remain unstated.

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 0%, so the description must carry the load. It explains the meaning of confirmed: true (separate account-holder confirmation gate) but says nothing about actionReference beyond "exact prepared booking", leaving the 64-hex reference format and provenance to the schema pattern alone.

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?

"Cancel one exact prepared booking" gives a specific verb and resource and implies the prepare-then-execute split that distinguishes it from prepare_booking_cancellation and execute_late_booking_cancellation. An agent can tell this is the terminal cancellation step for a single previously prepared booking.

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?

States clear preconditions: show the exact full preview, obtain separate account-holder confirmation, and pass confirmed: true; also warns not to retry automatically after a late-credit-loss warning. The only gap is that the sibling alternatives (prepare_booking_cancellation, execute_late_booking_cancellation) are not named as the paths for other cases.

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