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

Annotations already declare readOnlyHint=true, but the description adds real behavior: results are paginated via first/skip, values are returned as exact strings (relevant for precision-sensitive math), and 'Indexer data can lag' warns that results may be stale relative to on-chain state. No auth or rate-limit details, so not 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?

Three short sentences with the core capability first, then pagination mechanics, then the staleness caveat. Every clause carries information an agent needs; nothing is padded.

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-shape explanation is correctly omitted, and the read-only safety profile is covered by annotations. For a paginated 5-parameter indexer read the description is nearly sufficient, missing only guidance on which pool identifier form applies to V4 and how pagination termination is detected.

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 0%, so the description must carry parameter meaning; it explains only that first/skip bound each request (pagination) and that version selects V3 vs V4. The three required parameters — pool, chain_id, version — get no semantic detail (e.g., that a V4 pool is a 32-byte pool id while V3 is a 20-byte address, or what the six chain_id values mean), leaving a real gap against 0% schema coverage.

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: 'Fetch paginated initialized ticks and exact liquidityNet/liquidityGross strings for V3/V4'. Naming the per-tick liquidity fields distinguishes it from indexer-level siblings such as get_pool_liquidity and get_uniswap_charts without the agent needing to open 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?

Gives a concrete composition rule — 'combine with current pool liquidity and tick from prepare_uniswap_reads' — which tells the agent this tool is a building block for a depth chart rather than a standalone read. It stops short of naming alternatives (e.g., get_pool_liquidity) or saying when this tool is unnecessary, so no explicit exclusions.

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