prepare_morpho_withdraw_collateral

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

Annotations (destructiveHint=true, idempotentHint=true) are consistent, and the description adds critical behavioral context: returns handle+preview for Ledger, reverts if below liquidation threshold, and isolates exact amount logic. No contradictions with annotations.

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 five sentences, front-loaded with the core action, and each sentence adds essential information without redundancy. Perfectly sized.

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?

Even without an output schema, the description covers prerequisites, error conditions, operational details (no approval), and return format (handle+preview). Complete for a transaction preparation 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 coverage is 100% with descriptions, but the tool description corrects the schema's misleading allowance of 'max' in the amount parameter. It adds meaningful nuance (human-readable decimal, no 'max'), and explains marketId discovery. Slight deduction for schema contradiction.

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 it builds an unsigned Morpho Blue withdrawCollateral transaction to remove collateral. It explicitly distinguishes from siblings like prepare_morpho_withdraw by specifying 'collateral' and adding nuances like 'max not supported'.

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?

Explicitly advises querying get_morpho_positions first to know deposited collateral, explains why 'max' is unsupported, warns about liquidation threshold revert, and notes no approval needed. This provides complete usage guidance.

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