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

No annotations are provided, so the description carries the full burden. It usefully discloses the pay-per-call cost (from $0.002 USDC), which is real behavioral context the schema cannot express, but it omits read-only/mutation semantics, authentication requirements, rate limits, and failure behavior.

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?

Three compact sentences with the payload (what is returned) front-loaded, followed by routing detail and pricing. No filler, though the raw path strings are slightly noisy for a description field.

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 only two well-documented required parameters and no output schema, the description covers what is returned, which chains are supported, and the cost model. It is largely complete, with only the sibling-differentiation gap holding it back.

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 both parameters are already documented, giving a baseline of 3. The path listing does reinforce that 'id' is a mint on solana and an address on EVM chains, but adds little beyond the schema's own 'SPL mint or ERC-20 address' description.

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 resource (token) and enumerates what it returns: live price, liquidity, 24h volume, DEX pairs. However, it does not distinguish itself from siblings like solana_token, token_report, and solana_token_report, leaving the agent to guess which token-lookup tool is appropriate.

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 chain-to-path mapping implies which chains are queryable, but there is no explicit guidance on when to choose this tool over solana_token or token_report, nor any exclusions or prerequisites. Usage is left entirely to inference.

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