estimate_base_gas_safe

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

No annotations are provided, so the description carries the disclosure burden. It does reveal a cost/token requirement ('0.01 USDC on Base L2') and the safety-buffer behavior, but it does not explain how paymentSignature is used, whether external RPC calls happen, or what the response contains.

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?

One front-loaded sentence plus a short parenthetical; no filler. It packs the verb, resource, safety behavior, and payment signal into a compact definition.

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 complex enough (EIP-1559, L2, gas buffers, USDC payment) and has no output schema or annotations, yet the description leaves the payload content unspecified and never explains return format or payment mechanics. An agent would struggle to form a correct invocation from this alone.

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 100%, so the baseline applies; the schema documents both params. The description adds domain context but no concrete payload shape or paymentSignature usage, and the payload description in the schema is generic.

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 names a specific verb (Computes), a clear resource (EIP-1559 baseFee + priorityFee on Base L2), and a distinctive safety purpose (gas spike buffers to prevent stalled transactions). This is enough to differentiate the tool from gas-price and EVM siblings without opening schemas.

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 implies when the tool is relevant — when a safe, buffer-protected gas estimate is needed on Base L2 — but it never names alternatives or states when not to use it. The sibling list contains similar EVM/gas tools, so explicit routing would have helped.

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