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

Beyond the 'destructive' hint provided in annotations, the description explicitly states a critical operational behavior: the tool only performs an action if the 'confirm' parameter is true. This is a vital behavioral detail not captured in the schema or hints.

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 definition is highly concise and impactful. It uses strong, capitalizations ('DESTRUCTIVE') and front-loads the essential operational constraints.

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?

The description covers the scope (user's bookings), the trigger (confirm=true), and the nature of the operation (destructive), leaving no ambiguity about how or when the tool should be used.

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?

With 0% schema description coverage, the description adds significant semantic value by explaining that the operation is conditional on the 'confirm' flag and defining the ownership constraint (user-owned bookings).

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 a specific verb ('Cancels') and identifies the resource ('a booking'), making the purpose immediately clear to an agent.

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 provides a clear operational boundary by stating it only cancels bookings the user is part of, helping the agent avoid trying to cancel external bookings.

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