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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantial behavioral context: the exact billing model ($0.003 USDC per successful call, failed calls not charged), the payment rails (x402 on Base/Solana/Arc), decoded revert handling (Error(string), Panic(uint256)), and the state-override limitation of public RPCs. This is far beyond what the annotations convey.

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?

Strongly front-loaded: purpose first, then return shape, then caveats and price. Every sentence carries information, though the 'Information only, not financial advice' boilerplate is the one line that earns its place mainly as a compliance requirement rather than task guidance.

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 paid, read-only simulation tool with an output schema, this is complete: inputs, return contents, failure semantics, RPC limitation, and cost/payment model are all covered. Nothing an agent needs to call it correctly is missing.

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 enumerates the input fields and notes the conditional return ('token balance if to is an ERC-20'), but adds no format or syntax detail beyond what the schema already documents.

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 and resource ('Simulates an EVM transaction execution') and immediately distinguishes it from broadcasting siblings with 'without broadcasting'. An agent can tell it apart from evm_call, evm_tx, and rpc_evm without opening any schema.

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 phrase 'without broadcasting' implies the pre-flight use case, but there is no explicit when-to-use guidance, no named alternative, and no exclusion conditions. Usage is left to inference rather than stated.

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