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

With no annotations, the description carries the full load: it discloses the pool-selection heuristic ('deepest pool'), the chain set, and the returned fields, and 'read directly' signals a non-mutating call. It does not cover failure behavior when no pool exists, unsupported tokens, or whether the fee parameter overrides pool selection.

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?

A single front-loaded sentence that packs source, chains, and return fields with no filler. Every clause carries information.

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 the field list in the description is redundant-but-harmless, and the core read semantics are covered. Gaps remain around fee-parameter behavior, the default quote token (USDC), and edge cases, which matter given zero annotations and 0% schema coverage.

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 compensate: it confirms tokens can be given by 'symbol or address' and lists the valid chains for the chain param, which is real added meaning. However it says nothing about the fee parameter's role (it only lists fee tier as an output) nor the default token_out of USDC, leaving two of four params under-explained.

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+resource ('Spot price of a token pair') plus the exact data source ('deepest Uniswap v3 pool'), and enumerates supported chains. This clearly separates it from generic price tools like crypto_token_prices or dex_pairs by naming the protocol and the pool-selection rule.

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 on-chain spot pricing from the deepest pool, which tells an agent the general context, but it never says when to prefer this over sibling price tools (crypto_token_prices, crypto_price_history, orderbook_depth) or any prerequisites/exclusions. Usage is inferable but not stated.

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