withdraw_erc4626

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

No annotations provided, so description carries the burden. Discloses that withdrawal is a mutative action and explains 'max' behavior, but lacks details on permissions, reverts, or gas costs. Adequate but not thorough.

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 concise sentences. First sentence states purpose clearly; second adds useful usage tip. No superfluous words, front-loaded with key 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 simple withdrawal tool with 4 documented parameters and no output schema, the description covers the action and a key behavioral detail. Missing details like return value or prerequisites, but adequate given low complexity.

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 covers 100% of parameters. Description adds value by explaining the special 'max' value for amount and its liquidity implications, going beyond the schema's basic description.

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?

The description clearly states the verb 'withdraws' and resource 'assets from any ERC-4626 compliant vault', making the tool's purpose specific and distinct from siblings like deposit_erc4626, withdraw_aave, etc.

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?

Provides guidance on using 'max' for full withdrawal and mentions vault liquidity limitations, but does not explicitly differentiate when to use this tool versus other withdrawal tools (e.g., withdraw_aave).

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