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

Annotations already cover read-only/no-destruct, but the description adds genuinely new context: pricing ($0.01/call via x402 USDC or card key), first 25 free, failed calls free, and the non-obvious billing consequence that repeats are not free. It does not spell out behavior when no pool exists at a fee tier, which keeps it off 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 the resource and what is returned, then usage, then pricing. Dense but nearly every clause carries information; the billing sentence spills into the same paragraph as the read-only claim, slightly blurring the two ideas.

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 does the heavy lifting by enumerating returned fields and ordering (deepest pool first), which is exactly what an agent needs to interpret results. It omits edge-case behavior (pair not listed, no pools at a fee tier), 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 coverage is 100%, so chain/tokenA/tokenB are already documented, and the description largely restates them (0x address or ticker, chain list, worked example). It adds no format constraints or validation rules beyond the schema, so 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 resource (Uniswap v3 pools for a token pair) with concrete verb-like semantics (read live from the factory and each pool) and enumerates exactly what is returned: pool address per fee tier, prices, tick, in-range liquidity, balances, sorted deepest first. No sibling in the list covers Uniswap pool state, so differentiation is unambiguous.

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?

Gives explicit use cases: 'find the right pool, check depth before a swap or read a spot price,' plus a concrete example (tokenA=WETH, tokenB=USDC). It stops short of naming when-not-to-use or an alternative tool, but there is no sibling that competes for this job.

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