simulate_transaction

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

No annotations are provided, so the description bears the burden. It discloses the key behavioral trait: no actual transaction is sent. However, it doesn't mention whether it returns a boolean, a detailed error message, gas estimates, or state changes. It also doesn't state if it supports all networks listed or if simulation requires a funded account.

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, concise sentence that front-loads the core purpose and outcome. Every word earns its place; no fluff or repetition.

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 simulation tool with 5 parameters and no output schema, the description is adequate but leaves gaps. It doesn't explain what 'succeed' means (e.g., reverts, gas estimation failure), how to interpret the result, or whether this is a read-only operation. However, the schema's 100% coverage helps, and the core purpose is clear.

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 no extra meaning beyond the schema; the parameter descriptions in the schema are self-explanatory (e.g., 'recipient address', 'calldata as hex string'). The description doesn't clarify edge cases like 'value' formatting or network defaults, but the schema already covers this adequately.

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 'Simulate a transaction to check if it would succeed without actually sending it' uses a specific verb ('Simulate') and clearly distinguishes the tool from siblings like 'execute_swap' or 'send_private_transaction'. It states the core value proposition (check success without sending), making its purpose immediately clear.

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 usage: use this tool when you need to verify a transaction's outcome before committing. However, it doesn't explicitly exclude alternatives like 'estimate_gas' or 'simulate_bundle', nor does it state when not to use it. A clear context is provided but no alternative tools are named.

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