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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds relevant scope — it is an explanatory/knowledge tool constrained to eight named chains — though it does not say what form the answer takes or whether 'how to get it' involves any action.

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?

One front-loaded sentence delivers purpose, the triggering use case, an example, and the supported chains with no filler. It is dense — nested parentheses and the trailing chain list — but every clause carries information.

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 one-parameter, read-only lookup with no output schema, the description covers what is explained, the situation that warrants it, and the supported chains. Only the shape of the returned guidance is left unstated, which is a minor gap.

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% and the single enum parameter is fully documented with the same eight values the description lists. The description adds no format or selection nuance beyond the enum itself, so the baseline 3 is appropriate.

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: explains which coin pays network fees and how to obtain a little of it. The scenario ('tokens stuck because the wallet holds none of that coin') makes it unmistakably distinct from the sibling get_quote and track_swap tools, which handle pricing and swap tracking rather than guidance.

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?

Clearly names the triggering condition — a wallet holds zero of the fee coin and therefore cannot move tokens, with a concrete example (USDT on Tron with no TRX). It does not explicitly state when not to use it or point to a sibling alternative, so it falls short of a 5.

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