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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the description's job is to add context — and it does: per-call cost, latency character ('fast'), dual independent sources on Solana with the spread reported as a signal. It omits failure modes (unsupported chain, unknown token) and any rate-limit detail beyond the price hint.

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 where each clause carries information the agent needs: chain coverage, Solana dual-source spread, cost, polling use case. Dense em-dash/semicolon packing makes it slightly harder to scan than a two-sentence split would.

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 2-parameter read tool with full annotations and no output schema, the description covers what is returned (price, liquidity, spread) and the practical cost/latency tradeoff. Only edge-case behavior — auto-detect conflicts or unsupported mints — is left unaddressed.

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 100%, so both `mint` and `chain` are already documented including the optional-chain purpose and a chain list URL. The description's chain enumeration (Solana, EVM, Tron, Sui, TON) largely restates the schema, so it adds little beyond the baseline.

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 ('price and liquidity for a token') plus scope ('any chain'), and the 'fast / cheapest / built for polling' framing implicitly separates it from heavier siblings like get_token_snapshot and get_price_history. It stops short of naming an alternative, so an agent must infer the boundary rather than read it.

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?

'Built for polling' and 'Costs $0.01, the cheapest endpoint here' give clear selection context: use this for frequent, low-cost refreshes. No explicit when-not or named alternative is offered, so the agent gets context but not exclusion rules.

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