simulate_transaction_preflight

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: zero API key requirement, that it decodes custom revert reasons, and that it returns one of three recommendedAgentAction values. It omits failure modes (RPC errors, unsupported chains, rate limits), which keeps it from a 5.

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 tightly packed sentence-set that front-loads the key differentiator (ZERO API KEY REQUIRED) and the core action, with no filler. Every clause earns its place by adding a distinct capability.

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, the description does the work of enumerating the three possible recommendedAgentAction outcomes, which is exactly what an agent needs to branch on. Minor gaps remain around error/inconclusive behavior and chain-specific limitations.

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%, so all five parameters including the chain enum are fully documented in the schema. The description only gestures at the chain choice ('Base or Ethereum') and adds no syntax or format guidance beyond that, so baseline 3 applies.

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 ('Pre-flight EVM transaction simulator') plus the exact mechanism (eth_call + eth_estimateGas on Base or Ethereum). It is clearly distinguishable from the sibling decode_calldata_or_failed_tx, which handles post-hoc decoding rather than pre-broadcast simulation.

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?

'before signing/broadcasting' gives a clear temporal trigger for when to invoke, and the drainer-approval detection implies the safety-check use case. It stops short of naming an alternative tool or stating exclusions (e.g., what to do when simulation is inconclusive), so it is not a 5.

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