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

Annotations cover only readOnlyHint and openWorldHint, so the description carries real weight and does: it discloses the data source and pool type, the thin-liquidity trust caveat, the x402 pricing ($0.001 USDC per call, free failures, 3 free calls/day), and the quote-then-pay flow. This is exactly the behavioral context an agent needs before spending money.

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 core answer and cleanly sectioned under 'When to use', 'Use instead', 'Parameters', and 'Returns'. It is on the long side for a three-parameter tool, and the Returns paragraph partly repeats the liquidity/thin-pool detail already stated in the opening sentence, costing a point.

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 compensates by enumerating the return fields (price_usd, pool, liquidity, thin_liquidity flag), the chains, the pricing model, and the quote/pay workflow. An agent has everything needed to call it correctly and interpret the result.

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 3 is the baseline and the description's parameter section largely restates the schema ('SOL' on Solana, chain default). It earns one step above baseline by explaining the payment round-trip — omit `payment` to receive a quote, then sign and call again — which the schema only implies.

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 ('Get a token's current USD price'), names the supported chains, and discloses the non-obvious methodology (deepest on-chain pool via Uniswap v3 / Orca Whirlpools rather than a price API). It is clearly distinguishable from price_history, token_check, and crypto_market_pulse.

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?

Has explicit 'When to use' and 'Use instead' sections that route the agent to three named alternatives with the conditions that select each (past prices, price plus safety warnings, BTC/ETH/SOL batch). Nothing is left to inference.

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