prepare_morpho_withdraw

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds value by clarifying that the output is an unsigned transaction (no on-chain effect) and specifying the action (withdraws supplied loan token). It does not describe output format or failure scenarios, but this is acceptable given the 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 two sentences, front-loading the main action and including a key constraint and advice. Every word adds value with no redundancy.

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 DeFi transaction preparation tool, the description covers the core action, parameter constraint, and prerequisite (query position). It could mention prerequisites like balance or approval, but the advisory to query position partially covers this. With good annotations and schema, it is sufficiently complete.

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 description coverage is 100%, but the tool description adds context by clarifying the 'amount' parameter (no 'max' support) and linking 'marketId' to loan token withdrawal. This goes beyond the schema's descriptions, providing higher-level guidance.

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 'Build an unsigned Morpho Blue withdraw transaction' and specifies the resource ('withdraws supplied loan token'). It distinguishes from siblings by noting that 'max' is not supported, differentiating it from other prepare_* tools that may support 'max'.

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?

The description explicitly advises using an explicit amount and warns that 'max' is not supported, instructing users to query their position first. However, it does not explicitly mention alternatives like prepare_morpho_withdraw_collateral for collateral withdrawal, though the sibling list implies differentiation.

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