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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description still adds material context beyond that: the cancellation is local plus best-effort at Printful/Printify, and crucially that it does NOT refund on the sales channel. That refund caveat is exactly the kind of side-effect disclosure an agent needs.

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?

Front-loaded with the action, followed by the two consequential caveats (provider cancellation, no refund) and the usage guardrail. Efficient overall, but the trailing '[#9e800b]' artifact is stray noise that does not belong in the text.

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?

With no output schema, the description must carry behavioral weight, and it does: it explains what is destroyed (the local order and the provider-side draft/order) and what is explicitly not done (no refund). For a destructive mutation tool this is nearly complete; only the return shape is unaddressed, which is a minor gap.

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 description coverage is 100%, so both parameters (workspace, order_uuid) are already documented in the schema. The description adds no syntax or format detail beyond the schema, so the baseline of 3 for a schema-covered tool is appropriate.

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 and resource (cancel an order) and immediately scopes what is actually cancelled: locally plus best-effort at the fulfillment provider. This clearly differentiates it from adjacent siblings such as hold_order, approve_order, unapprove_order, or reconcile_order.

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 an explicit guardrail -- 'only cancel when the user explicitly asks' -- which is real when-to-use guidance. It does not, however, name a non-destructive alternative (e.g., hold_order) an agent should prefer when cancellation is not explicitly requested.

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