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

Goes well beyond the annotations by disclosing data provenance (DefiLlama), staleness (cached 5 min), rate limits (30 calls/hour per client), and a paid x402 path with price and endpoint. This is exactly the operational context an agent needs to decide whether to call and how to handle throttling. Nothing contradicts readOnly/openWorld/non-idempotent hints — live pricing naturally explains idempotentHint=false.

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 the verdict taxonomy and metrics; the caching, rate-limit, and x402 pricing clauses each carry decision-relevant information. It is a dense single paragraph with a long URL, but no sentence is pure filler.

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 compensates by naming the verdict enum, score range, bps deviation, supply windows, and liquidity. It does not specify the top-level response shape (e.g., array vs object for multi-asset queries), which is the only remaining gap 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?

Schema description coverage is 100%, so both `asset` (symbol/name/DefiLlama id/CoinGecko id, up to 10 comma-separated) and `chain` are already fully documented in the schema. The description only alludes to per-chain output via 'per-chain liquidity' and adds no new syntax or semantics. Baseline 3 is correct.

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 resource (USD stablecoin peg health) and enumerates the exact verdict outputs (PEGGED / WATCH / DEPEG_RISK / DEPEGGED) plus the metrics returned. An agent knows precisely what it gets back. The sibling tools are all unrelated validators, so no differentiation burden exists and none is needed.

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?

Scope limits are explicit: USD stablecoins only, 'live' verdicts, 'informational only, not financial advice'. That tells the agent when the output is appropriate. There is no named alternative or when-not-to-use condition, but the tool has no competing sibling, so the practical gap is small.

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