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

With no annotations, the description carries the full burden. It helpfully discloses the method (eth_call pool discovery), the excluded segment (majors), the limitation that V3 depth is estimated, and that results are informational only, but it omits quote freshness, failure modes, and return format.

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?

Four compact sentences, front-loaded with the core purpose, then method, exclusions, and caveat. There is no redundant filler, and each sentence adds relevant context.

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 cross-chain quote tool with no output schema and no annotations, the description gives a useful operational overview and limitations. It remains incomplete about how to supply the token parameter and what the returned quote looks like, which an agent needs in order to invoke it correctly.

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 0%, so the description must explain the parameters. It names the three supported chains, which partially reinforces the chain enum, but does not explain the token parameter's expected format (e.g., contract address) or any additional 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 specifies the resource and scope precisely: quotes for long-tail EVM tokens from public DEX pools on three named chains, with majors excluded. It is easy to distinguish from sibling utility tools, though it never states a direct action verb or names an alternative tool.

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?

It implies usage for long-tail tokens and explicitly excludes majors, and it labels the tool 'Informational only.' However, it does not state when to prefer it over an alternative or describe prerequisites such as having a token address.

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