1s_estimate_gas

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

No annotations provided, so the description carries full burden. It discloses that the return is a hex value and that reverts return the revert reason. It does not cover potential side effects or authorization needs, but given the tool is a read-only estimate, the description is adequate.

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. It is front-loaded with the purpose and immediately useful usage guidance. No unnecessary words.

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 description explains the return format (hex) and behavior on revert. Given no output schema, this is sufficient. It could mention that the estimate is for the current state and may vary, but overall it covers the essential context for an agent to use it correctly.

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 coverage is 100%, with each parameter described. The description does not add new parameter-level meaning; it only adds a note about return value. Baseline 3 is appropriate as the schema already documents parameters 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 clearly states the tool estimates gas via eth_estimateGas. It specifies the resource (transaction gas) and the action (estimate). This distinguishes it from siblings like 1s_simulate_call which executes a call, and other live query tools.

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 recommends using this tool before sending transactions to set gas limits. It also notes that reverts return the revert reason. However, it does not mention when not to use it or provide alternatives (e.g., when to use simulate_call instead).

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