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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true; the description adds the human-meaningful consequences ('hard to undo'), the required OAuth scope, and the confirmation protocol. It stops short of stating what actually happens to the order (status change, refund, inventory restock), which matters for a destructive write.

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 clauses, front-loaded with the risk flag and ending with the endpoint. No sentence is redundant and an agent can parse the safety posture in the first two words.

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 2-parameter destructive write with full annotation coverage and no output schema, this covers safety, prerequisites, confirmation, and transport. The one meaningful omission is the post-cancellation state, which an agent may need to report back to a user.

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%, so the baseline is 3; the confirmation instruction goes beyond the schema by flagging the id-vs-order-number trap at the point of invocation. It adds no detail on reason formatting beyond what the schema's min/max length and example already convey.

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') with a scope qualifier ('optional reason') that maps directly onto the two parameters. The 'WRITE' prefix immediately separates it from the many read-oriented easystore_get_*/list_* siblings.

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 a concrete pre-call workflow ('Confirm the order id and number with the user first') and a hard prerequisite ('Needs write_orders'). It does not name an alternative or suggest a read-only verification step such as easystore_get_order, which is the obvious sibling pairing for a destructive action.

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