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

Annotations already mark destructiveHint=true, and the description goes further by stating the action is irreversible and instructing to confirm with the guest. This adds meaningful context about consequences beyond the annotation, though it doesn't detail other potential side effects.

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 two sentences, front-loaded with the core action, and every clause contributes meaning. It efficiently conveys purpose, prerequisite, and warnings without 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?

Given this is a simple destructive tool with one parameter and no output schema, the description is fully complete. It covers what the tool does, where the input comes from, the irreversible nature, and a required user confirmation, making it sufficient for an AI agent to invoke correctly.

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?

The schema provides 100% coverage for the token parameter, including its origin from create-booking. The description repeats this without adding extra semantic detail, so it provides no value beyond the schema baseline.

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 uses the specific verb 'Cancel' with the resource 'an existing booking', making the action unambiguous. It also specifies the required management token from create-booking, distinguishing it from sibling tools like get-booking-info or list-available-slots.

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 clearly states the prerequisite (token from create-booking) and advises confirming with the guest before calling, which acts as a usage guardrail. It doesn't explicitly name alternatives or exclusions, but the sibling context makes it evident this is the sole cancellation tool.

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