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

Adds real behavior beyond the annotations: per-hash independent reporting, the rule that unknown/already-terminal/not-yours does not abort the rest, and that the operation is hosted and terminal with no broadcast or gas. It does not address how the confirm_order_cancel sibling relates to this call, or the tension between the idempotencyKey parameter and idempotentHint=false.

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 operation and the cap, then the positioning, then the failure semantics, then the no-gas note – a sensible order with no sentence that carries no information. The re-quoting-ladder illustration is slightly florid, but it is the sentence that justifies the tool's existence.

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 destructive batch mutation with an output schema and full annotation coverage, the description supplies everything needed to call it correctly: scope, sibling routing, partial-failure contract, and the absence of on-chain steps. The only gap is the relationship to problee_confirm_order_cancel, which the description never mentions.

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 the schema already documents every parameter including the 50 cap, duplicate collapsing, nonce, signature challenge and idempotency key. The description's only parameter claim ('up to 50') repeats what maxItems already states, so baseline 3 applies.

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 with a hard scope bound ('Cancel up to 50 named orders in one call') and immediately positions itself between 'cancelling one hash' and 'cancelling everything'. An agent can distinguish it from problee_cancel_order and problee_cancel_all_orders without opening either schema.

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 alternatives are named explicitly and the selecting condition is given: when you need more than one hash but not a full book teardown (the re-quoting-a-ladder scenario). The only thing left implicit is that a single hash should go to the single-order tool, which the positioning makes obvious.

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