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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered. The description adds genuinely useful non-schema context: the underlying GET route and a $0.01 cost per call. It does not itself explain the 402 challenge retry behavior, but that is documented in the payment parameter's schema text.

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?

A single front-loaded sentence plus endpoint and price — no filler. It is dense to the point of being slightly telegraphic ('Live gas on ... plus USD transfer cost'), but every fragment 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 zero-required-parameter read-only lookup with full schema coverage, the description covers scope, chains, cost, and route. The only gap is that with no output schema the description does not characterize the response shape (units, per-chain fields), which would help an agent interpret results.

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 chain enum plus the payment/402 flow are fully documented in the schema, so the description has nothing left to add. Mentioning '?chain=' duplicates existing schema information rather than extending it, so the baseline 3 applies.

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 the resource (live gas prices) and enumerates the exact six chains covered, plus an extra value-add (USD transfer cost). It is clearly distinguishable from siblings such as get_btc_fees or get_crypto_prices, though it never names them explicitly and uses a noun phrase rather than a verb.

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 description gives no when-to-use or when-not guidance and does not point to alternatives like get_btc_fees for Bitcoin fees. The only contextual hint is the endpoint path and the $0.01 price, which tells the agent the call costs money but not when it is the right call.

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