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

Adds significant context beyond annotations: explains sequential state propagation, per-step results including gas and revert reasons, net movements, and the crucial caveat that state can change so success is evidence, not guarantee. No contradiction with annotations.

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?

Description is well-organized: first sentence states purpose, second details outputs, third gives input guidance, fourth warns about state changes. Every sentence earns its place without redundancy.

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?

Complete for a simulation tool: covers input format, output, and caveats. Output schema exists, so return details are covered. No missing critical information for correct invocation.

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 baseline is 3. The description adds valuable guidance on constructing steps, specifying they should come from prepare_action or related functions, and clarifies optional value and gas in wei. This elevates it above baseline.

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 clearly states the tool simulates a sequence of transactions against the latest Base block before signing. It uses a specific verb ('simulate') and resource ('list of transactions'), and the context 'before anything is signed' distinguishes it from siblings like prepare or status.

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 provides clear context: use to preview before signing, and instructs to pass steps exactly as returned by prepare_action, invest_usdc_to_gblin, or swap_gblin_to_usdc_jit. However, it doesn't explicitly mention alternatives or exclusions, so it relies on implicit differentiation.

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