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

Discloses two traits annotations do not cover: the tool is paid ($0.001 USDC on Base per successful call via x402) and it is a live snapshot that can inform waiting. The payment rail plausibly explains the readOnlyHint=false annotation, though the description never says whether calls fail if payment is absent, which leaves a minor gap.

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?

Two sentences, front-loaded with the returned values, then the use case and pricing. Every clause earns its place with no filler.

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 zero parameters, no output schema and no nested objects, the description fully covers what an agent needs: what is returned, why to call it, and the fact that it costs money. Nothing material is missing.

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?

The tool takes no parameters (schema is an empty object at 100% coverage), so there is nothing to document; baseline 4 applies. The description correctly implies a zero-argument, network-scoped call.

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 (current gas on Arbitrum One) and enumerates exactly what is returned: gas price, base fee, suggested priority fee in gwei, and the cost of a 21,000-gas ETH transfer. The chain name 'Arbitrum One' cleanly separates it from the many sibling *_gas tools (base_gas, eth_gas, op_gas, polygon_gas).

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?

Gives explicit timing guidance: 'Use before sending a transaction or to decide whether to wait.' That is a clear use context, though it never names an alternative tool or states when this is the wrong choice (e.g. L2 vs L1 gas queries).

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