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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description adds genuinely new behavioral facts: an empty result is still charged, a first eligible cached call is free, and paid calls cost $0.001 USDC via x402. It does not cover rate limits or retry/pagination semantics, so it stops short of 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?

Front-loaded with purpose and scope, then returns, then the empty-result edge case, then cost. Every sentence carries information, though the payment sentence is dense and could be split for scannability.

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 usefully enumerates the return fields (pool address, DEX, USD price, volume, TVL, FDV, price change, tx count) and disclaims the empty case. Missing result caps/pagination and any explicit chain-filtering hint, so not fully 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 description coverage is 100%, so both parameters are already documented, including the x_payment challenge/retry flow. The description restates the match keys (symbol/name/address) already present in the query schema and adds no format or syntax detail beyond it — the baseline 3 applies.

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 ("Search DEX pools"), enumerates the eight supported chains, and names the three match keys (symbol, name, contract address). This is unambiguous against siblings like otto_stock_pools or otto_holder_analytics 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?

The description sets a boundary ("Pool discovery only; not a recommendation") but never names an alternative tool or a when-not condition, so the agent must infer routing from the name alone. The x402 free-vs-paid rule does describe a cost-driven usage condition, which lifts it above bare minimum.

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