gas_price

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

No annotations are provided, so the description carries the full burden, and it does so well by disclosing pricing ($0.002 USDC per call) and p99 latency (3000ms) upfront along with the exact data returned. It stops short of mentioning auth requirements or rate limits, keeping it from a 5.

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?

Front-loaded with the purpose, then payload details, params, cost, and latency in a single dense but organized block. Every clause earns its place, though the run-on structure is slightly heavy.

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 and no annotations, the description fully shoulders the burden by enumerating the return fields, the cost, the latency, and the parameter default. An agent has everything needed to call and interpret this tool.

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 description coverage is 0%, so the description must compensate, and it does: it names 'chains' as optional with a default of all chains. The allowed chain values are already enumerated in the schema enum, so no further explanation is needed for a single well-covered 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?

Specific verb+resource: 'Current gas prices' across a named set of chains, plus a precise enumeration of the returned metrics (gas price, base fee, priority fees, native token USD, transfer cost estimates). An agent can distinguish this from crypto_prices or btc_fees immediately.

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 word 'Current' implies fresh gas data and the default-all chains behavior is stated, giving implied usage. However, there is no explicit when-to-use/when-not guidance or routing to alternatives such as btc_fees or exchange_rates.

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