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

No annotations are supplied, so the description carries the full disclosure burden. It documents the authorization/payment model, the exact returned fields, ordering by detections, and defaults/maximum for key inputs. It does not explicitly clarify read-only behavior or side effects, but it is substantially more transparent than a minimal or code-driven description.

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 text is compact and information-dense: auth/payment, output fields, result ordering, and input defaults all fit in three short sentences. The main structural weakness is that the tool's purpose appears after the lengthy payment sentence, so it is not strictly front-loaded.

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 three-parameter tool with an output schema, the description covers core result fields, ordering, chain, defaults, limits, and access requirements. The main gaps are the absence of deeper active_hours semantics and any 'when-not-to-use' or alternative-tool context.

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?

The schema has no per-property descriptions, so the description adds real value by documenting active_hours default 168, limit default 50, and limit max 200. However, it does not explain what active_hours or limit formally represent beyond their names, and the chain parameter is left almost entirely to the enum.

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 identifies a specific resource — active MEV bot addresses on a chain — and enumerates the returned content: detections, strategy types, first/last seen, and a high-confidence flag. It lacks an explicit verb like 'list' or 'return' and does not differentiate it from sibling tools like mev_intel, so it doesn't earn full marks.

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 gives useful invocation context: an API bearer token or payment requirement, permissible chains, defaults, and limits. However, it does not explicitly state when to use this tool versus close siblings such as mev_intel, nor provide exclusions or alternative routing guidance.

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