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

Despite readOnlyHint=true, the description adds real behavioral context the annotations don't convey: it returns unsigned transactions in order, and nothing is signed or sent here. It doesn't cover auth requirements, vault prerequisites, or failure modes, keeping it at a 4.

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 sentences with zero filler, and the core action and modes are front-loaded ahead of the non-obvious unsigned-transaction caveat.

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 helpfully covers the return shape (ordered unsigned transactions) and confirms nothing is sent. It stops short of describing what per-transaction fields the caller receives, which an agent would need to know to chain signing steps.

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 high (83%), establishing a baseline of 3, and the description adds value by explaining the undocumented 'max' flag ('everything (max: true)') and that 'amount' is in base units. It still doesn't clarify the mutual exclusivity or precedence of amount vs max.

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 ('Withdraw ... from one of the owner's orderbook vaults to their wallet') plus the two modes (exact base-unit amount or max). This clearly separates it from read siblings like wallet_holdings and from order-entry siblings like place_limit_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?

The description gives clear operating context: it withdraws from the owner's orderbook vault to their wallet and returns unsigned transactions for the user to sign. It does not explicitly name an alternative tool or state when-not to use it, so it falls short of a 5.

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