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

With no annotations, the description carries the full behavioral burden. It usefully discloses the non-broadcast, read-only nature and the underlying RPC method, which is genuinely valuable. But it omits auth requirements, failure/revert behavior, and how the estimate is returned, so it is only partially complete.

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?

A single front-loaded sentence stating purpose, method, and the no-broadcast guarantee with no wasted words. Efficient, though it could have used a second short sentence for the parameter/value details it currently lacks.

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?

For a one-parameter read tool with no annotations and no output schema, the description covers purpose and the key non-broadcast behavior but leaves parameters and return/troubleshooting semantics thin. Adequate but with clear gaps.

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 0%, so the description must compensate, yet it only echoes the field names (to/from/value/data) that already appear as schema properties. It adds no format or semantic detail — e.g. that data is calldata hex or value_wei is in wei — leaving the nested payload underspecified.

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?

States a specific verb+resource (gas estimate) and scope: Base mainnet swaps or any call, via eth_estimateGas. Clearly says it does not broadcast. It doesn't explicitly name siblings like base_simulate or base_call, so it stops short of a 5, but the purpose is unambiguous.

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?

Implies when to use it (when you want a gas estimate without sending a transaction), which is useful context. However it never names the alternative tools (base_simulate, base_call, base_pending) or states when-not to use it, leaving the agent to infer the boundaries.

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