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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'reads or computes only' repeats structured data and earns no credit. The description does add genuinely new behavioral context, however: the cost model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) and the warning that repeats are not free, which meaningfully explains the idempotentHint=false flag. Nothing contradicts the annotations.

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-loads the resource and both modes in the first sentence, then usage, then pricing, in a logical order with no filler. The pricing sentence is long and slightly repetitive ('each call is charged, so repeats are not free' restates the per-call fee), keeping it from a 5.

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 available, the description usefully enumerates the returned fields (TVL, share of total, native token, chain id) and caps the result set at 100. It covers both modes and cost, leaving only minor unknowns such as whether the ranking is sorted descending or how failures surface.

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%, with both parameters documented (chain by name, limit 1-100 default 25), so the baseline is 3. The description reinforces the intent of omitting chain to get the ranking and supplies the example chain=Base, but adds no syntax, casing or validation detail 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?

States a specific resource (TVL per blockchain from DefiLlama) plus both operating modes: a ranked list of up to 100 chains with share of total, native token and chain id, or a single chain by name. That level of specificity distinguishes it from chain-agnostic siblings like defi_tvl without the agent needing to open either 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 concrete selection guidance: 'Use to compare L1s and L2s, size an ecosystem or pick where to deploy,' plus a worked example (chain=Base). It stops short of naming an explicit alternative or a when-not condition (e.g. protocol-level TVL via defi_tvl), so it lands just under the top band.

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