mev_sandwich_risk_simulator

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Simulates' hints at no on-chain execution, and the parenthetical gives pricing/network context, but the description omits whether paymentSignature is required, whether external RPC calls are made, what happens on invalid payloads, and whether there are any 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 dense, front-loaded sentence followed by a relevant pricing/network parenthetical. It wastes no words, though a small amount of usage or input detail would make it more informative without bloating it.

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?

There is no output schema and no annotations, and the only parameter is an opaque JSON string. The description names three computed outputs but does not explain expected payload structure, payment requirements, failure behavior, or output format, leaving an agent under-equipped to invoke it correctly.

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 the baseline is 3. The description adds some meaning by indicating the payload concerns pending swaps and Uniswap v3/v4 tick liquidity, but it does not specify the payload schema or any fields beyond the generic string description in the input schema.

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 uses a specific verb 'Simulates' and names a concrete resource: pending swaps against Uniswap v3/v4 tick liquidity. It lists three concrete outputs — sandwich vulnerability, maximum extractable value, and safe slippage limits — which clearly distinguishes it from generic quote or slippage sibling tools.

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 use case is implied: call this when you need MEV sandwich-risk assessment for pending Uniswap swaps. However, there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as compute_uniswap_v3_quote or calculate_dex_slippage_bounds.

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