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

Annotations only say read-only and open-world; the description adds substantial context beyond them: cost ($0.002/call via x402, USDC on Base), that errors are not charged on Base but other rails may charge, upstream sources (eth_feeHistory with eth_gasPrice fallback), cache cadence, and a buyer-terms link. This is exactly the payment/auth/freshness detail an agent needs before spending money.

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?

Purpose and the response field list are front-loaded, and each clause carries distinct information (fields, source, fallback, price, freshness, terms). It is dense to the point of being a wall of text in one paragraph, but no sentence is 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?

There is no output schema, and the description compensates by enumerating the returned fields (baseFeeGwei, priorityFeeGwei with p10/p90, suggestedMaxFeeGwei, timingHint, simpleTransfer cost, ethUsd). With freshness, pricing, and error-charging behavior also covered, an agent has everything needed to call and interpret it.

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?

Zero parameters, so the baseline is 4; the description correctly confirms 'no parameters' and instead spends its words on the response shape, which is the more useful information here. Nothing about parameter meaning is missing because there are none.

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?

Opens with a specific verb+resource+scope: 'Gas price API for Base and Ethereum: base fee, priority fee and a max-fee suggestion in one GET, no parameters.' No sibling tool covers gas pricing, and the description makes that scope unambiguous.

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?

States explicitly that it takes no parameters and that 'calling more often returns the same values' with data refreshing about every 1 min, which tells the agent when to call and when not to bother. It also clarifies the output is 'descriptive, not a forecast.' It stops short of naming a sibling alternative, but none in the list is a plausible substitute.

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