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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-schema context: a fixed cost ($0.005 USDC per call), the x402 payment mechanism, the free-trial/payment-requirements fallback, and that results are ranked by liquidity rather than arbitrary order.

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?

Two sentences plus a parenthetical price note, with the core purpose front-loaded before the resolution example and the payment detail last. No sentence is redundant and the cost disclosure is compact rather than buried in prose.

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 carries the burden of describing returns and does so ('most liquid matching pairs with contract addresses'), and it explains the payment gate that would otherwise cause a surprising failure. It stops short of covering result counts, pagination, or what happens on no-match/multi-chain ambiguity.

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 q, chain, and payment are already documented in the schema, including the enum-like chain examples. The description adds no syntax or formatting detail beyond that, so the baseline of 3 applies; the 'most liquid matching pairs' note informs result ranking, not parameter behavior.

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 ('Find tokens by name, symbol or address across chains') and clarifies the downstream outcome: resolving a ticker like 'BONK' to a contract address. It implicitly separates itself from price/pairs siblings by emphasizing identity resolution over market data, but 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?

The resolution use case ('so an agent can resolve BONK to a mint') gives an implied trigger for calling it, which is more than nothing. However, there is no guidance on when not to use it, and no pointer to siblings like token_price, token_pairs, or solana_token_safety that an agent might confuse it with.

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