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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the burden is lower. The description adds real substance beyond them: the exact formula (newHF = currentHF × (1 − drop%)) and the output behavior (per-position HF changes plus AT RISK / DANGER / LIQUIDATED flags). It stops short of stating protocol coverage limits or failure modes for non-lending wallets.

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?

Front-loaded with purpose, then the formula, then output shape, then usage cues — a sensible ordering. The four example queries are somewhat repetitive and could be trimmed, but each reinforces a distinct framing (single-asset drop, market crash, stress test, liquidation proximity).

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?

An output schema exists, so return values need not be described, yet the description still summarizes them helpfully. With two fully documented required parameters, full annotation coverage, and stated scope across five protocols, nothing an agent needs to invoke this correctly is missing.

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 meaning beyond the schema by explaining collateral_drop_pct as a wholesale collateral-value multiplier via the newHF formula, clarifying that the pct applies to the entire collateral side rather than a single asset.

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 (simulate) and resource (impact of a collateral price drop on active EVM lending positions), and names the protocols covered (Aave V3/V4, Spark, Morpho, Euler, Moonwell). An agent can distinguish it from calculate_health_factor (static current HF) and the scan_* siblings without opening any schema.

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?

Gives explicit triggering conditions via four natural-language user queries ('What happens to this wallet if ETH drops 30%?', 'Would this wallet survive a 40% market crash?', etc.), which is strong when-to-use guidance. It does not name an alternative tool (e.g., calculate_health_factor for the no-drop case) or state when NOT to use it, so it falls short of the 5 bar.

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