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

Annotations already declare readOnlyHint=true and destructiveHint=false, which is consistent with a prepare-only tool that builds calldata without submitting. Beyond that the description adds real behavioral context: the result is a ready-to-sign transactions array, and a vault-share approval transaction may precede the withdraw and appears under requirements. It stops short of covering ordering guarantees or whether the caller must sign every returned transaction.

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?

Four short sentences, front-loaded with purpose and then return shape, with no filler. Each sentence carries distinct information, though the final sentence about requirements could be tightened to clarify what the field actually contains.

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?

With no output schema, the description usefully sketches the return shape (transactions array plus requirements) and flags the possible approval step. However, for a transaction-preparation tool the description leaves open what the requirements field means, whether transactions are ordered, and how errors surface when the position is insufficient.

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 only 25%, with just "amount" documented, so the description should compensate more than it does. It does reinforce "max" for a full withdrawal, but says nothing about the human-readable decimals convention, chain enum behavior, or the vaultAddress/userAddress roles.

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?

States a specific verb and resource ("Prepare a withdraw from a Morpho vault") and names the return artifact, which separates it from read-only siblings like morpho_get_vault_positions. It only implicitly distinguishes itself from morpho_prepare_blue_withdraw and morpho_prepare_force_withdraw, so an agent must infer the vault-vs-market boundary.

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 never says when to pick this over morpho_prepare_redeem, morpho_prepare_force_withdraw, or morpho_prepare_blue_withdraw, all of which are plausible alternatives in the sibling list. The only conditional guidance is the "max" option, which is about an argument value rather than tool selection.

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