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

Annotations cover the read-only and open-world profile, and the description adds material behavior beyond them: the call is paid ($0.003 USDC on Base via x402), which is critical for an agent to know before invoking. It also signals coverage limits (requires a DEX pool), though it omits rate limits or failure behavior.

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 tight sentences, front-loaded with what the tool returns, followed by scope and cost. Every sentence carries information; the pricing sentence is arguably dry but operationally necessary.

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 read-only single-parameter tool with no output schema, the description covers the return payload (price + liquidity), source venues, coverage scope, and payment requirement. Only the detailed response shape is left implicit, which is acceptable given no output schema is declared.

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 0% (no per-parameter descriptions), but the description compensates by establishing that the single input is a Base token contract address and even supplies the ERC-20-style context behind the schema's 0x+40-hex pattern. The one required parameter is unambiguous from the prose.

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 states a specific resource and verb-equivalent (retrieve live token price on Base) and adds exactly what is returned: USD price and pool liquidity from Uniswap v2/v3 and Aerodrome. It implicitly separates itself from its sibling base_token (generic token data) by naming the price/liquidity scope, though it never names an alternative 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?

"Works for any token with a DEX pool, including newly launched ones" gives real context on applicability, implying failure for tokens without a DEX pool. However, it gives no explicit when-not-to-use guidance and never routes to alternatives such as base_token or base_token_risk.

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