withdraw_erc4626

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

No annotations are provided, so the description carries full burden. It mentions that the vault may limit to available liquidity, but does not disclose other behaviors like approval requirements, transaction outcomes, or potential reverts.

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 that front-loads the purpose and includes a clarifying note about 'max' usage. No redundant or unnecessary words.

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?

No output schema is present; the description does not mention return values (e.g., transaction hash, withdrawn amount). It also omits important context like slippage, approval flow, or error conditions, which are critical for a DeFi withdrawal 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 covers all parameters with complete descriptions (100% coverage). The description adds the behavioral nuance about maximum withdrawal being limited by vault liquidity, which is not in the schema, but does not provide significant new semantic detail beyond what is already in the parameters.

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?

Description clearly states the tool withdraws assets from any ERC-4626 compliant vault. It uses a specific verb and resource, and distinguishes from siblings like deposit_erc4626 and other withdraw tools by specifying the vault standard.

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 a usage hint for 'max' amount but lacks explicit guidance on when to use this tool versus alternatives like withdraw_aave or withdraw_compound, and does not mention prerequisites such as vault allowances.

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