prepare_morpho_withdraw

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

The description adds context beyond annotations by specifying the transaction is unsigned, the token type (supplied loan token), and the constraint on amount ('max' not supported). No contradiction with annotations is present.

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?

The description is highly concise, using a single sentence plus a clarifying note. It front-loads the core purpose, making it immediately actionable without any redundant 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?

Given the tool's complexity and lack of output schema, the description covers essential aspects: purpose, amount constraint, and a hint to query positions. It could mention the need to send the transaction afterwards, but the description is largely sufficient.

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?

With 100% schema coverage, the description still adds value by clarifying that 'max' is not supported and suggesting to query positions for the marketId, enhancing the schema's details.

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 explicitly states the tool builds an unsigned Morpho Blue withdraw transaction for a supplied loan token, clearly distinguishing it from sibling tools like prepare_morpho_borrow or prepare_morpho_supply.

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?

It explicitly warns that 'max' is not supported and advises querying positions first, providing clear when-to-use guidance. However, it could explicitly mention alternatives for max withdrawals, such as using a different tool or manual calculation.

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