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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description earns credit by adding that the checkout_id is released, that the call is a no-op on webhook-confirmed orders, and that recovery requires a fresh cart. It does not state idempotency (re-cancelling an already-cancelled checkout) or auth requirements.

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?

Four short sentences, each doing distinct work: action, trigger, no-op boundary, recovery path. The action is front-loaded with no filler.

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?

Output schema exists, so return values need no explanation; the tool takes one required param and the description covers trigger, effect on the resource, no-op case, and how to restart. An agent has everything needed to call this destructively and correctly.

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 100% and the single parameter already documents itself as 'checkout_id returned by create_checkout'; the description merely echoes that provenance. Baseline 3 applies when the schema fully carries parameter semantics.

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 ('Abort an unpaid checkout') and adds the lifecycle position (after create_checkout, before payment), which makes the operation concrete. It never mentions the sibling cancel_cart, so the checkout-vs-cart distinction is left implicit as the only sibling differentiation gap.

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?

Gives clear triggering context ('Use if the customer changes their mind after create_checkout but before completing payment') and a boundary condition ('Has no effect on orders already confirmed by webhook'). It also names the recovery path (new cart and checkout from scratch), but offers no guidance against cancel_cart for cart-level aborts.

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