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

No annotations are provided, so the description carries full responsibility. It discloses key behaviors: cancellation does not move money, releases the client_reference (allowing reprint), and handles race conditions by returning not_cancellable rather than falsely claiming success.

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 a single dense paragraph, front-loaded with the core purpose. Every sentence adds distinct value, but the length is substantial; a structured list could improve scannability.

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?

Given the complexity of cancellation semantics, the description covers all relevant scenarios, effects, and errors. It also references the appropriate sibling tool for refunds, making it self-contained despite the lack of an output schema.

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 schema provides descriptions for order_token but not order_id. The description enhances understanding of order_token's role and alternates, and explains error conditions. order_id is implied as the order to cancel, but its origin is not explicitly stated beyond context.

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 opens with 'Cancel an order, stopping it before it is printed', a specific verb and resource that clearly distinguishes this from siblings like create_order and get_order. It continues with concrete state-based behavior, further differentiating from related tools.

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?

Provides explicit when-to-use guidance: cancel works while awaiting_payment with order_token, and platform-created orders can be canceled even in confirmed/printing states. It also states when not to use it (shipped/delivered cannot be canceled) and directs to refund alternatives via get_catalog.

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