get_current_gas

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

No annotations are provided, so the description carries full burden. It discloses the exact outputs (gas prices, ETH/USD, recommendation). However, it does not mention data freshness, source, or any limitations (e.g., mainnet only, potential caching). Still, it is mostly transparent for a simple read tool.

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 consists of two concise sentences. The first states the purpose, the second gives a use case example. No wasted words, and information is front-loaded.

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 no parameters, no output schema, and no annotations, the description is fairly complete. It covers what the tool returns and when to use it. It could mention that it is for Ethereum mainnet only (though implied) and any refresh policy, but overall it is sufficient.

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 tool has zero parameters, so baseline is 4. The description adds meaning beyond the empty input schema by explaining the returned data, which is valuable for an agent.

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 retrieves current Ethereum mainnet gas price (low/average/high in Gwei), live ETH/USD price, and a send-now-vs-wait recommendation. This specific verb+resource differentiates it from siblings like get_eth_price (ETH price only) and get_l2_gas (L2 gas).

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 says to use this tool to answer 'what is the gas fee right now', providing a clear use case. It does not explicitly mention when not to use or alternatives, but the sibling context implies differentiation. A slight improvement would be to exclude other cases.

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