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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds the one thing annotations cannot express — that no charge is incurred — which is the key consequence an agent needs; it does not say what happens to the checkout state afterwards, which would have made it a 5.

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?

Two short sentences, zero filler, with the action stated first and the reassuring consequence second. Nothing to trim.

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 simple two-parameter cancel tool with no output schema and reasonable annotation coverage this is close to adequate, but it omits the resulting checkout state, behavior on non-open/already-completed checkouts, and any session_id sourcing guidance.

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 coverage is only 50%: api_key is documented in the schema, but session_id has no description and the tool description does not compensate at all — it never mentions what a session_id is, where to obtain it, or that the api_key is optional when the connection carries one.

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+resource ("Cancel an open checkout") and scopes it to open checkouts, which implicitly separates it from complete_checkout and get_checkout. It does not explicitly name siblings, so it stops short of the top score.

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?

Usage is implied by the "open" qualifier and by the sibling set, but there is no explicit when-to-use/when-not guidance (e.g. what to do if the checkout is already completed or expired) and no prerequisites are stated.

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