gas-prices

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

No annotations are provided, so the description bears full responsibility. It clearly states data sourcing (free public RPC endpoints), that no API key is needed, and lists the returned data for all 6 chains. It implies read-only, safe operation with no side effects, which is adequately transparent.

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?

The description is concise (3-4 sentences) and front-loaded: first sentence gives purpose and scope, second details returned data, third covers source and access, fourth summarizes use cases. Every sentence adds value with no redundancy.

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?

Given the simple input schema (1 optional param), no output schema, and no annotations, the description fully covers purpose, input semantics, output content, data source, use cases, and supported networks. It is complete for an agent to decide when and how to invoke the tool correctly.

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 only parameter 'networks' has full schema coverage (type, description). The description adds context beyond the schema: default queries all 6 chains, and specifying a subset yields faster responses. This helps the agent optimize usage without needing extra inference.

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 tool returns current gas prices and EIP-1559 fee recommendations across 6 specific EVM chains. It lists the exact data returned (base fee, priority fee percentiles, estimated cost) and the supported networks, making it distinct from sibling tools focused on other crypto metrics.

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?

The description explicitly advises when to use the tool: 'before sending on-chain transactions, estimating agent operating costs, or comparing chain fees for routing decisions.' It misses explicit mentions of when not to use it or specific alternatives, but the use cases are well-defined.

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