Current gas price and EIP-1559 fee estimate

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful context: the cost ($0.001 per call) and the specific EIP-1559 fee estimate. This goes beyond the annotations without contradicting them. No mention of rate limits or response format, but the core behavioral traits are well covered.

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, zero wasted words. The first sentence front-loads the purpose and supported chains. The second sentence adds pricing as a secondary detail. Each sentence earns its place.

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?

The tool has no output schema, but the description indicates the return type ('current gas price and EIP-1559 fee estimate'). For a simple one-parameter tool, this is sufficient. It could be more precise by mentioning units (e.g., gwei), but the overall completeness is high given the tool's simplicity.

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 description does not add any meaning beyond the schema's enum and default. The description lists the same chains already in the schema. Baseline 3 is appropriate as the schema already adequately documents the parameter.

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 clearly states the verb ('get') and resource ('gas price and EIP-1559 fee estimate') for specific chains (Base, Ethereum, Polygon, Arbitrum, Optimism). This differentiates it from siblings like get_crypto_price, which returns token prices, not gas fees. The title reinforces the purpose.

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 guidance is provided on when to use this tool versus alternatives. Siblings include get_crypto_price and get_crypto_market_data, which could be confused for gas-related queries. The description only lists supported chains but does not exclude other tools or explain prerequisites (e.g., chain must be in the enum).

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