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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals the pricing model (free via MCP, pay-per-call alternative for production), but says nothing about rate limits, window bounds, data source, or freshness — significant gaps for a tool whose reliability profile matters.

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 substantive capability before the commercial note. The promotional URL is arguably incidental to tool selection, but the text is otherwise tight with no wasted words.

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 no output schema, the description usefully enumerates the returned statistics, covering the return-value question. The parameters are fully documented in the schema, so the remaining omission — data source and freshness guarantees — is a modest gap rather than a blocking one.

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 single parameter windowMinutes is fully documented in the schema (100% coverage), so the schema does the heavy lifting. The description's phrase 'over a window' corroborates the parameter meaning but adds no syntax, bounds, or default information beyond what the schema already supplies.

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?

The description names a specific resource (Ethereum gas price) and enumerates exactly what is computed (rolling average/min/max/volatility/trend), which lets an agent distinguish it from siblings like get_gas_history_export or get_normalized_gas. It does not, however, explicitly state how it differs from those tools, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance relative to the sibling gas tools. The mention of a pay-per-call production endpoint is about the delivery channel, not about choosing this tool over get_gas_comparator or get_normalized_gas, so it does not function as usage routing.

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