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

The description repeatedly asserts the operation is 'Permanent' and irreversible ('A cancellation is permanent'), which describes a destructive update. The annotation declares destructiveHint=false (i.e. only additive updates), so the description contradicts the structured metadata. Despite otherwise rich context (side effects, confirmation policy, auth), the contradiction forces a 1.

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 purpose is front-loaded, but the text is redundant: permanence is asserted twice ('Permanent' and 'A cancellation is permanent') and the OTA/channel rule is restated in near-identical terms, inflating length without adding information.

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 one-parameter destructive tool with no output schema, it covers constraints, side effects (room becomes available, reservation remains listed), policy warnings, per-call confirmation, and API-key requirements. It is nearly complete, lacking only return/response detail.

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?

Only one parameter, and schema description coverage is 100% with a concrete example (LH12345) already in the schema. The description adds no format or syntax detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (Cancel) and resource (reservation) with a precise scope: 'a Confirmed Front Desk reservation.' It clearly distinguishes itself from siblings like list_reservations, get_reservation, and update_reservation_status by naming the exact state it acts on.

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?

Explicitly states when it works and when it fails: OTA/Channel reservations must be cancelled on the channel, Direct Booking ones under Direct Booking, and checked-in/checked-out ones need a status change first. It routes the agent to the correct alternative in every blocked case.

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