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

With no annotations, the description carries the full burden and does so well: it discloses the authentication model (ChainHelix API key or per-call microroyalty over Binance b402/x402), the hard caps (window max 1440, limit max 500), the covered chains, and even that every hash re-derives from a public RPC. This is unusually rich behavioral disclosure for a read endpoint.

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 middle sentence enumerates every returned field in a single sprawling clause, and the payment preamble leads before the purpose. It is dense and slightly disorganized, though nothing is strictly wasted given the auth and limit details.

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?

An output schema exists, so the field-by-field enumeration is partly redundant, yet the description still covers auth, filters, chain coverage and limits. Adequate for an agent to invoke correctly, with mild over-explanation of return values.

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 0%, so the description must compensate, and it does: pool filtering, the four type enum values, the chain set, window units (minutes) with default 60 and max 1440, and limit default 50 with max 500. Defaults and bounds are not present in the schema at all, so the description adds real meaning.

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 resource: the extracted MEV victim order flow for one chain, newest first, including victim/attacker hashes, pool, gas and profit. That is specific and distinct from generic siblings like mev_pressure or market_state. It stops short of explicitly naming which sibling to prefer, so it is clear but not fully differentiated.

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?

It tells the agent it can filter by pool and by type (sandwich, backrun, frontrun, jit), and documents the window/limit bounds, which implies the calling context. However there is no explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named.

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