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

Beyond the destructive/openWorld/idempotent annotations, the description discloses what actually happens: immediate cancellation plus a customer email for unconfirmed/unpaid bookings, a request passed to the business for confirmed/paid ones, and the Terms-based free-cancellation windows (24h transfers, 48h tours). The instruction to get customer confirmation before calling is exactly the kind of pre-flight context annotations cannot convey.

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?

Four sentences, front-loaded with the action and the confirmation gate, then the branch behavior and terms. Every sentence carries decision-relevant information with no padding.

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, open-world mutation with no output schema, the description covers the key gaps: the two outcome paths, the customer notification, the fee-free window, and the confirmation requirement. An agent has enough to call it responsibly.

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%, so bookingId and email are already fully documented (including that email proves ownership). The description only restates that both are needed and never mentions the optional 'reason' parameter, so it adds little beyond the schema — baseline 3.

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 ('Cancels a booking') and scopes it to the customer's explicit request, which separates it from request_booking and change_booking. An agent can tell immediately what this tool does and what it is not.

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?

It clearly says when to call (customer-initiated cancellation, after asking the customer to confirm) and describes the two behavioral branches — auto-cancel for unconfirmed/unpaid vs. a forwarded cancellation request for confirmed/paid. It stops short of naming sibling alternatives such as change_booking for modifications, so it is strong but not exhaustive.

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