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

The description reconciles the readOnlyHint=true annotation by explaining this is an 'unsigned step' that only constructs the payload — the wallet signs and sends it. It also discloses that cancel-all uses Seaport incrementCounter rather than per-order cancellations, a real behavioral difference. It stops short of noting that incrementCounter permanently invalidates all orders/gas implications.

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?

Two dense sentences with the core action front-loaded and no filler. The parenthetical stacking ('(hash)', '(all = true, Seaport incrementCounter)') is slightly cramped but every clause carries information.

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 3-parameter tool with full schema coverage and no output schema, the description covers what it does, the two modes, and the unsigned-payload contract. The only mild gap is not stating explicitly that the return value is an unsigned transaction payload to be signed.

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, but the description adds meaning beyond the schema by framing 'hash' and 'all' as mutually exclusive cancellation modes and explaining the incrementCounter mechanism behind 'all = true'. It does not clarify what happens if both or neither of hash/all are supplied.

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 open order on the X Layer voucher market — and explicitly covers both modes (single order by hash, or all open orders). The distinction from siblings like xl_post_order/xl_build_order is obvious from the verb alone.

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?

Clearly indicates the two usage paths: pass 'hash' to cancel one order, or 'all = true' to cancel everything. It does not name a sibling alternative or state exclusions, and it does not say what the caller should do with the returned unsigned payload beyond the wallet signing it.

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