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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the description doesn't need to repeat that. It adds valuable context: cost per call ('$0.01/call, x402') and a disclaimer ('Not financial advice'). However, it could disclose rate limits or error handling for invalid addresses/tickers.

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?

The description is concise (3 sentences) and front-loads the core action and outputs. Every sentence adds value: outputs, source, prerequisites, cost, and disclaimer. Minor critique: the cost line could be integrated more naturally with the first sentence.

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?

Given the absence of an output schema, the description compensates by listing key return fields (liquidity, 24h volume, pair age, quality score, risk flags). It also covers prerequisites and cost. However, for a tool with 100 max items and 4 parameters, additional context on pagination or output format limits would enrich completeness.

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 the schema fully documents all four parameters. The description does not add new parameter-level semantics beyond listing outputs. Per guidelines, baseline 3 is appropriate since the schema covers everything, but the description could enhance usage examples (e.g., mixing addresses and tickers in one call).

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 specific verbs ('Look up', 'get liquidity, 24h volume...') paired with a clear resource ('token contract address or ticker across DEXes'). It also lists concrete outputs that distinguish it from sibling tools (e.g., rug-pull-scorer, live-price-oracle) by focusing on liquidity, volume, pair age, quality score, and risk flags.

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 provides context by stating the data source ('Powered by DexScreener's public API') and indicates constraints ('No key, no wallet, no on-chain node'). It does not explicitly mention when not to use it or name alternative sibling tools (e.g., for on-chain analysis), which would elevate the score to 5.

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