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

Annotations already declare readOnly/openWorld/idempotent and non-destructive, so the safety profile is covered. The description adds useful context: a per-call cost of $0.005 and that prices are live-RPC sourced. However, it does not disclose the two-step payment requirement (call without proof, then retry), which is a significant behavioral trait left entirely to the parameter schema.

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 tightly scoped sentence with no filler; the cost is front-loaded in brackets and the chain list is explicit. Every phrase adds 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 tool with a 100%-covered schema, the description plus schema contains what an agent needs: chains, cost, source, and the payment handshake. The absence of an output schema is not a gap since the dimension explicitly says it needn't explain return values. Minor missing context would be an explicit note that payment is required; however, that is fully specified in the parameter description.

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%: the single optional 'payment' parameter has a detailed description explaining the EIP-3009 proof and the call-once-then-retry flow. The tool description itself adds no parameter-level information, which is acceptable at the 100% coverage baseline.

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?

Description states the tool provides live gas prices for three specific chains, making the resource and scope clear. It lacks an explicit verb like 'fetch' or 'get,' but the noun phrase 'Live gas prices' unambiguously signals a retrieval operation. None of the 14 sibling tools overlap with gas price data, so sibling differentiation is not required.

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?

No when-to-use or alternative-routing guidance is given; the description simply states the service. While it implies use when current gas prices are needed, it does not mention any prerequisites, alternatives, or exclusions. The payment flow is documented only in the schema, not as usage guidance.

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