Cancel Checkout Session

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

No annotations are provided, so the description carries the full disclosure burden. It mentions the cart-clearing side effect and the return status 'canceled', which explains what will happen. It does not cover error behavior or idempotency, but the core behavioral outcome is transparent.

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 description is compact and well-structured with purpose, usage, Args, and Returns sections. The primary action is front-loaded, and every sentence earns its place 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?

For a simple one-parameter tool, the description covers purpose, usage context, parameter provenance, side effects, and return format. The only gaps are edge cases like invalid or already-canceled sessions, which are minor for correct invocation.

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 input schema only says session_id is a string, with 0% schema description coverage. The description compensates by explaining where to get session_id ('From create_checkout_session result'), which gives the agent usable sourcing information beyond the bare type.

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 clearly states a specific action ('Cancel') and resource ('checkout session'), and adds the side effect of clearing the cart. This distinguishes it from sibling tools like create_checkout_session, update_checkout_session, and complete_checkout.

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?

The description explicitly says when to use it: when the user wants to abandon a checkout or start over. It does not name alternative tools, but the intended context is unambiguous given the checkout-related sibling tools.

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