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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, and the description adds substantial context beyond them: the exact payment model ($0.05 per call over x402 on Base), the auth mechanism (prepaid x-credit-token header for unlimited calls), the absence of a free tier, and "No API key required." This is precisely the cost/auth/rate-limit disclosure the rubric credits.

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 key decision framing and the risk-factor list are front-loaded, and no sentence is filler. There is avoidable redundancy, though: the vault requirement is stated twice ("vault= required" and "Required input: vault"), and the disclaimer phrase sits mid-paragraph.

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 single-parameter read tool with an output schema, an agent needs purpose, the input, and the payment/auth path — all present, plus a preview of the verdict values it will receive. Nothing material is missing for correct invocation.

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?

There is a single parameter with 100% schema description coverage ("MetaMorpho vault address"), so the schema already carries the semantics. The description only restates the requirement ("vault= required", "Required input: vault") without adding format or validation detail, which is the baseline 3 case.

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 opens with a decision framing ("Should you deposit into this MetaMorpho vault?") and then states a concrete verb+resource: it reads the vault's live allocation, idle share, performance fee, timelock and control metadata and returns a diversified/concentrated/control_risk verdict. The scope (vault-level deposit risk) is specific enough to separate it from position-oriented siblings like morpho_health and morpho_liquidatable.

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 gives clear usage context — "the read before parking funds in a yield vault" — which tells the agent exactly when to reach for it. It does not, however, name an alternative or state a when-not condition (e.g. vs morpho_health), so it stops short of the explicit routing a 5 requires.

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