erc4337_userop_gas_estimator

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states what is computed and includes a cryptic parenthetical fee ('0.040 USDC on Base L2'), without explaining whether an on-chain call is made, how payload errors are handled, or what paymentSignature actually triggers in terms of settlement and side effects.

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, front-loaded sentence with a clear verb and output fields. The parenthetical fee note is slightly cryptic and not fully explained, but it does not make the description bloated.

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 complex ERC-4337 gas estimation tool with no output schema and no annotations, the description should specify payload format, required UserOperation fields, and expected result shape. The generic 'payload' schema description does not provide enough information for an agent to invoke the tool correctly with confidence.

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 is 3. The description adds output-domain context about gas limits and paymaster overhead, but it does not clarify how to construct the payload or what paymentSignature behavior is expected.

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 and resource: it computes exact ERC-4337 UserOperation gas limits. It also enumerates the outputs (verificationGasLimit, callGasLimit, preVerificationGas), which clearly distinguishes it from generic EVM gas tools like estimate_base_gas_safe.

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 identifies the target use case: ERC-4337 Account Abstraction UserOperations with paymaster gas safety overhead. This gives clear context, though it does not name excluded cases or alternatives, so it stops short of a 5.

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