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

Annotations mark readOnlyHint=true on what sounds like a sell, and the description proactively resolves that tension: it returns an UNSIGNED transaction and 'nothing happens until you sign it', plus 'Liquid never holds keys or funds'. That is exactly the context annotations cannot convey. It does not cover rate limits or failure modes, so 4 rather than 5.

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?

Tight and front-loaded: the action, the two payout modes, the prerequisites, and the return shape all land in the first half. It is dense but every clause carries information; no filler or repetition.

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 transaction-building tool with a full input schema, an output schema, and safety annotations, the description supplies the remaining unknowns an agent needs: chain (Base), fee (Free), custody model, and the unsigned-then-sign workflow. Nothing required to invoke it correctly is missing.

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 vault, inKind, shares, and minUsdcOut are all documented in the schema itself; the baseline is 3. The description adds only the general 'no vault needed' framing, which arguably sits oddly against the required vault parameter, and adds no format or units detail beyond the schema.

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 ('redeem basket shares to USDC, or take the raw stock tokens in-kind') and immediately contrasts the two exit paths. An agent can distinguish this from stocks_buy and stocks_send without opening any 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?

Gives real context for when this applies: 'works any block, no vault needed, anyone holding shares can sell', which tells the agent this path has no vault-deployment prerequisite. It does not explicitly name a sibling alternative or an exclusion case, 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.