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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds real substance: it explains the detection method (front-run + back-run in surrounding transactions) and scopes the read to "recent" history. It stops short of stating scanning depth/window limits or expected latency, so it is strong rather than exhaustive.

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?

Three short sentences, front-loaded with the core action, then the mechanism, then the routing constraint. Every sentence adds distinct information with no repetition of the schema or annotations.

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 annotations covering safety and an output schema covering return values, the description only needs to establish purpose, method and routing, which it does. Minor residual ambiguity (how far back "recent" reaches, chain default) is documented in the schema rather than here.

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% for both parameters (address and optional chain defaulting to base), so the schema already carries the parameter semantics and baseline 3 applies. The description only implies the address input and gives no detail on the chain default or the time window behind "recent transactions."

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 pair ("Batch scan an address's recent transactions") plus the exact target of the analysis (MEV sandwich attacks, front-run + back-run patterns). It explicitly distinguishes itself from the sibling security.mev.shield, so an agent can separate the two without opening either 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?

Gives both sides of the routing decision: use this for historical inspection of sandwich patterns around an address, and explicitly "It is not a pre-trade protection decision; use security.mev.shield before a swap or liquidity action." The when-not plus named alternative is exactly the guidance needed.

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