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

The destructiveHint=true annotation already tells the agent this is a destructive mutation; the description adds nothing beyond that, such as whether cancellation is reversible, whether held inventory is released, or whether a cancelled checkout can be resumed. With annotations present the bar is lower, but the description restates the name rather than enriching it.

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?

A single front-loaded sentence with zero waste, but its brevity reflects under-specification rather than disciplined editing. There is no structural signal, such as prerequisites or a note on what the call returns.

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?

This is a destructive mutation with two parameters, no output schema, and an undocumented required ID. The description provides none of the state, permission, or post-condition context an agent needs before invoking it.

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 'id' parameter has no schema description, and the description never says what it identifies (presumably a checkout ID) or what format it takes. With only 50% schema coverage, the description needed to compensate and does not.

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 ('a checkout'), which is clearly distinguishable from siblings like complete_checkout or update_checkout. It stops short of specifying scope, such as whether it works only on pending checkouts or applies to any state.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The most relevant sibling, complete_checkout, is an obvious fork in the road (cancel vs. finalize) that the description never addresses.

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