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

Goes well beyond the annotations by explaining the counterintuitive readOnlyHint=false ('not marked read-only because each call is charged'), which prevents an agent from mistaking it for a free read. Adds pricing/rate-limit context ($0.002/call via x402, first 25 free, failed calls free) and confirms it 'reads or computes only'.

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-loads the payload (what is read/computed, in what units) followed by usage, then pricing. It is long for a gas tool, but nearly every clause carries distinct information; the pricing sentence is the only one that could be trimmed.

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 parameters, the description carries the full burden and delivers: it enumerates each returned metric and its unit (gwei vs wei), the block context, and the fee estimates. An agent knows exactly what it gets back and what it costs.

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 takes zero parameters, so the baseline is 4; there is nothing param-related for the description to clarify. The description's detail about returned fields is descriptive value rather than parameter semantics.

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?

Names the specific network (Base / chain 8453) and enumerates exactly what is produced: base fee, priority fee, maxFeePerGas, maxPriorityFeePerGas, block fullness, and execution-fee estimates in specified units. This cleanly distinguishes it from the sibling *_gas tools for other chains.

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?

States explicit usage moments: 'Use before sending a transaction on Base or to decide whether to wait for lower fees.' It gives clear context but never names an alternative tool (e.g., base_tx or base_block) for adjacent checks, so it stops short of full when-not/alternative guidance.

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