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

Beyond readOnlyHint=true, the description discloses real behavior: the plan uses exact-approval semantics, the max share price is enforced onchain as ERC-4626 inflation protection, shares are minted only to the sender, and 'the server performs no data fetch' — meaning the tool does not verify state itself. The weak point is that it does not say what the tool returns (an unsigned plan) or that signing/broadcast is out of scope, though the output schema covers the return shape.

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?

Two dense sentences, front-loaded with the action and the route, with no filler. It is jargon-heavy (RAY, VaultBundlesV1, ERC-4626) but each clause carries information an agent needs.

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 7-parameter prepare tool with a fully documented schema and an output schema, the description supplies the crucial missing context: the price input must come from fresh state and the server does no fetching of its own. It omits only the downstream handoff (sign/submit the returned plan) and any slippage/price-staleness failure modes beyond the onchain guard.

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%, so the baseline is 3; the description adds value by explaining why max_share_price_ray must be freshly derived and how it is enforced onchain, and by reinforcing that shares go to the sender (constraining recipient). It does not add anything on amount, deadline, or chain_id beyond the schema.

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 states a specific verb and resource ('Prepare an exact-approval Morpho Vault V2 deposit') and names the exact route ('official SDK's VaultBundlesV1'). It distinguishes itself from redeem/withdraw siblings by the word 'deposit' but never names an alternative tool explicitly, so differentiation is implicit rather than stated.

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?

Usage context is implied rather than spelled out: 'the caller supplies a fresh RAY-scaled max share price' signals the agent must first read onchain vault state, and the schema points to get_morpho_vaults for the address and chain. There is no explicit when-to-use/when-not guidance versus prepare_morpho_vault_redeem, prepare_morpho_vault_withdraw, or direct-approval flows.

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