base_gas_estimate

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (fetching current gas prices with tiers) but does not mention potential side effects, rate limits, or caching behavior. For a straightforward read-only operation, this is adequate but not rich in contextual detail.

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 a single concise sentence, front-loading the action and resource, and includes the essential detail of output tiers. Every word adds value with no fluff.

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 is very simple, with no parameters and an output schema to describe return values. The description covers the core purpose and key output attributes (Gwei, tiers). It does not add extra caveats, but given the low complexity, it is sufficiently complete.

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 0 parameters, so the schema fully covers them (vacuously). The description adds no parameter-specific details, but none are needed. Given the baseline of 4 for zero-param tools, this scores well.

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 uses a specific verb 'Get' with a clear resource 'current Base L2 gas prices in Gwei' and specifies the output tiers (safe/recommended/fast). This distinguishes it from siblings like base_price, which likely pertains to token prices rather than 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 clearly implies this tool is for fetching gas prices on Base L2, and the presence of 'gas' differentiates it from token price tools. However, it does not explicitly compare itself to alternatives or state when not to use it, but the context is sufficiently clear for a simple read-only tool.

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