prepare_lido_unwrap

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

Description adds 'no approval needed' and 'burns wstETH from caller's balance' beyond annotations. Annotations already indicate destructive and idempotent, but description enriches behavioral context.

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?

Single sentence, no fluff, efficient delivery of purpose and key behavioral trait.

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, description covers purpose, mechanism, and safety (no approval). Missing details on stETH destination, but sufficient for a build-transaction tool.

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 has 50% coverage; amountWstETH is well-described, wallet has no description. Overall description does not add parameter details beyond schema. Minimal extra value.

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?

Clearly states it builds an unsigned wstETH.unwrap transaction converting wstETH to stETH. Specific verb and resource differentiate from siblings like prepare_lido_wrap.

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?

Implies usage for converting wstETH to stETH, but lacks explicit guidance on when to use vs alternatives like prepare_lido_unstake. No direct mention of exclusion criteria.

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