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

With no annotations, the description carries the full burden and does it well: it discloses the data source (deepest Uniswap V3 pool via eth_call), the chains covered, the fields returned for auditability, and a concrete cost/payment mechanism ($0.005 per call over x402 in USDC). Missing only failure behavior when no pool exists and rate/latency characteristics.

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 source, followed by return fields, trust/cost notes. Dense but each sentence contributes (source, chains, auditable outputs, cost). Only slightly packed with the x402/payment detail in the same breath as the technical source.

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 3-param read with no output schema, the description itself enumerates returned fields (pool address, fee tier, liquidity, sqrtPriceX96, tick, block) and the pricing model, which is what an agent needs. It stops short of documenting no-pool failure modes, the one gap given the absence of annotations and output schema.

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 the schema already documents chain, quote, and token; the baseline is 3. The description adds minor context (quote defaults to USDC, token is an ERC20 contract) but no syntax, format, or edge-case guidance beyond what the schema states.

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 (reads spot price) and resource (any ERC20), plus the exact source mechanism (deepest Uniswap V3 pool against USDC) and supported chains. This clearly separates it from sibling reads like evm_token_info, evm_balance, or evm_erc20_balance, which return metadata/balances rather than a priced quote.

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 conveys context (no aggregator, no API key, on-chain source) so an agent can infer this is the price tool, but it never explicitly names alternatives or states when NOT to use it, e.g. for tokens with no V3 pool or on unsupported chains. Usage is implied rather than routed.

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