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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low, yet the description adds real behavior: a TVL ≥ $10k filter, ordering by best 7-day net APR ('best first'), a ranking caveat warning that low-TVL pools can top the list, and case-insensitive, order-agnostic symbol matching.

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?

A single dense sentence, front-loaded with the resource and filter, followed by ranking behavior and matching rules. Every clause carries information, though the length makes it slightly run-on rather than crisply segmented.

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 read-only lookup with no output schema, the description adequately conveys what comes back (pools with their best range by 7-day net APR). Gaps remain around the chain filter's effect and any result-count limits, but the core call semantics are complete.

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 67% (tokenA/tokenB have examples, chain is enum-only with no description). The description compensates usefully by specifying that symbols match case-insensitively and in either order, clarifying the two required params, but it says nothing about how the optional chain parameter limits the search.

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+resource ('Every listed pool of a token pair') plus exact scope: across chains, DEXes and fee tiers with a TVL ≥ $10k floor. This is clearly distinguishable from the sibling list_pools, since it is scoped to a token pair rather than all pools.

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?

The description implies the use case (look up all pools for a pair, ordered by best 7-day net APR) and even gives an interpretation caveat ('a small pool can rank first, so weigh tvlUsd'). It does not explicitly say when to prefer a sibling such as list_pools over this tool, so routing is left partly to inference.

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