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

readOnlyHint already establishes that this is a safe read, but the description adds two pieces of genuinely behavioral context: the data mirrors the open source Uniswap interface's GraphQL fields, and an empty series signals missing indexed data rather than zero volume. It does not disclose timestamp bucketing granularity or rate limits, but it exceeds what the annotations alone convey.

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?

Two sentences with no filler: the first front-loads what is returned and over what window, the second delivers the one caveat an agent needs. Nothing is repeated from the title or schema.

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-value shape need not be explained, and the empty-series caveat covers the main interpretation pitfall. However, for a tool with three required identifier parameters at 0% schema description coverage, omitting any explanation of chain/version/pool or of the duration enum's meaning leaves meaningful gaps.

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 needs to carry parameter meaning and it does not. Only 'duration' is referenced, and even there it does not clarify whether the enum selects a lookback window or a bucket size; chain_id, version, and pool semantics (especially the 40- vs 64-hex pattern) are left entirely to the schema.

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?

The description uses a specific verb and resource: 'Fetch timestamped token0/token1 prices and USD volume history over the requested duration.' This is clearly distinct from sibling pool-metadata reads such as get_uniswap_pool or get_uniswap_pool_ticks, although no sibling is named explicitly.

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?

There is no statement of when an agent should choose this tool over alternatives (e.g., get_pool vs get_uniswap_pool_ticks vs quote_uniswap_liquidity), and no prerequisites or exclusions. The only guidance present concerns interpreting an empty result, not selecting the tool.

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