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

Goes well beyond the readOnly/openWorld annotations: discloses data provenance (DexScreener aggregate rather than raw on-chain reads), an explicit limitation (slippage not computed), and a full payment model ($0.002 USDC per successful call via x402 on Base/Solana/Arc, failed calls not charged). An agent cannot get any of this from the schema or 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-loaded with the core purpose and metric list, then terse caveats and pricing. Three dense sentences with no filler, though the pricing sentence is long and could be tightened slightly.

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 fields need not be explained, and the description covers provenance, limitations, and cost. Minor gaps remain: behavior when a pool is not indexed or a chain is unsupported, and whether data is real-time or cached, are not stated.

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 `pool` and `chain` documented including a chain slug example, so the schema carries the parameter burden. The description reinforces the one-pool/one-chain constraint but adds no format or validation detail beyond the schema, making the baseline 3 appropriate.

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 (live pool snapshot from DexScreener) scoped to exactly one pool address on one chain, and names the coverage set (Uniswap, Raydium, Curve and other indexed DEXes). This clearly separates it from sibling tools like crypto_uniswap_v3_ticks, crypto_curve_gauge_weights, and crypto_balancer_v2_pools, which return protocol-specific internals rather than an aggregate pool snapshot.

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 usage context ('for one pool address on one chain') and notes slippage is not computed, which hints at when it is insufficient. But it never explicitly says when to pick this over siblings such as uniswap_v3_ticks or the various quote tools, nor does it state prerequisites (supported chain slugs, pool must exist).

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