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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so safety is covered. The description adds genuine behavioral context beyond them: sort order (by liquidity), pricing ($0.02/call over x402 on Base), the prepaid x-credit-token header for unlimited calls, one free call/day, and no API key requirement.

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 core action ('All DEX pools for a token, deepest first') followed by returned fields and then payment details. Every sentence carries information, though the pricing/access sentence is somewhat dense and could be trimmed.

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?

An output schema exists, so return values need not be detailed, yet the description still enumerates the key fields. Combined with the pricing/access terms and the single well-documented input, an agent has everything needed to call it correctly.

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% for the single parameter, so the schema already documents 'address' as a token contract address. The description only restates that the address is required, adding no format or constraint detail beyond the schema. 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 ('Lists every DEX pool for a Base token') plus the scope ('All DEX pools... deepest first'). Names the concrete fields returned and the chain, so an agent can distinguish it from siblings like pair_info or dex_spread without opening a 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?

Implies usage via 'Tells agents where — and how deep — a token can be traded,' which signals the intent to find trading venues. However it names no alternative sibling (e.g., pair_info, exit_liquidity, dex_spread) and gives no when-not-to-use condition, leaving routing to inference.

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