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

Beyond annotations (destructiveHint=true, idempotentHint=true, openWorldHint=true), the description discloses the crucial preview behavior: the first call cancels nothing, returns the refund and a confirmation_token, and cancellation is irreversible. This is exactly the kind of operational safety context an agent needs before invoking a destructive tool.

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 usage condition and workflow, then adds irreversibility and an example. Every sentence contributes operational value, and there is no redundant restatement of the tool name or annotations.

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 a destructive, multi-step tool with five parameters and an output schema, the description covers the prerequisite chain, preview semantics, confirmation requirements, irreversibility, and input source for the non-obvious parameters. An agent has enough information to call it safely without needing to infer destructive behavior.

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 description coverage is 60%, and the description adds meaningful semantics for the key parameters: confirm controls preview vs execution, management_id comes from verify_reservation_management, confirmation_token comes from the preview, and reservation_number is conditional on account connectivity. It does not explain the market parameter, which is the main gap.

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 states a specific verb and resource ('cancel' a reservation) and immediately distinguishes the supported invocation paths (management_id vs reservation_number) from sibling tools like verify_reservation_management. An agent can tell exactly what this tool does without opening the schema.

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 gives explicit when-to-use conditions, prerequisites (verify_reservation_management or a connected BEEP.rent account), and a step-by-step flow: call without confirm, show the refund, obtain explicit yes, then call with confirm=true and the token. The alternative input paths are also clearly delineated.

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