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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real context by attributing the source (AlphaGrowth) and noting the data is free, which tells the agent no auth or cost is involved. It does not mention rate limits or freshness/staleness of TVL figures, which keeps it from a 5.

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 sentences, front-loaded with what is returned before the cross-tool guidance; every clause carries information (fields, page size, slug handoff, data source). No 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 enumerating the returned fields, and the pagination/query semantics live in the schema. For a two-param read-only list tool, nothing an agent needs to call it 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% and both parameters already carry descriptions ('Page number, 50 chains per page' and the substring-match query), so the description's '50 per page' repeats the schema. It adds only the downstream meaning of the chain slug, which is a marginal gain over the structured fields.

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 and resource ('Blockchains ranked by TVL') plus the exact fields returned: price, market cap, 1d/7d TVL change, project counts, and page size. An agent can distinguish this chain-listing tool from chain_metrics or rank_projects 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?

Explicitly routes the agent downstream: use the chain's slug with chain_metrics and its chain_slug as the filter for rank_projects. That names the alternatives and the handoff condition, though it doesn't state when this tool should be skipped in favor of a project-oriented search like find_projects.

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