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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral context: the cost per call ($0.005 USDC via x402), chain coverage, sorting criterion, and returned fields. It does not detail rate limits or error behavior, but the key financial and scoping traits are disclosed.

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 two sentences, front-loaded with the core purpose and followed by the cost detail. Every element earns its place: the chain examples clarify scope, the metric list specifies output, and the pricing sentence is essential for invocation.

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 moderate complexity, full schema coverage, annotations, and no output schema, the description provides enough for an agent to call the tool correctly: it states chain coverage, sorting, returned metrics, and cost. It omits details like pagination or result limits, but those are minor gaps for this type of tool.

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 parameters (token and payment) are already well documented in the schema. The description adds only high-level context ('for a token on any chain') and does not elaborate on the payment parameter or address formats beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 clearly states that this tool returns top DEX trading pairs for a token across multiple chains, sorted by liquidity, and lists the metrics included. It is specific enough to distinguish it from a simple price lookup, though it does not explicitly name sibling alternatives like token_price.

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 tool's intended use is implied by 'Top DEX trading pairs for a token on any chain,' but there is no explicit guidance on when to choose this over token_price, token_sell_check, or other token-related siblings. The payment context is mentioned, but no when-not conditions are provided.

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