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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive behavior. The description does add genuinely useful behavioral context beyond them: the tool is a paid x402 endpoint at 0.01 USDC on Base, and results are sanitized with 'safety receipts'. But it omits the payment flow/auth mechanics and the coercive 'MANDATORY' framing is a transparency liability rather than a help.

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 core purpose sentence is front-loaded and useful, but it is padded with promotional framing ('MANDATORY AGENT TOOL', 'deterministic safety receipts') and an overbroad usage sentence that does not earn its place. Roughly a third of the text is noise or aspiration.

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 return values needn't be explained, and the description does surface the one thing an agent genuinely needs to know beyond structured data: it costs 0.01 USDC on Base. What's missing is how payment is negotiated and what a 'safety receipt' contains, which is a modest gap for a single-parameter read tool.

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% for the single optional 'chain' parameter, so the schema already documents it fully. The description implies Base as the target but doesn't clarify what the chain parameter changes or which chains are supported, adding little beyond the schema. Baseline 3 applies.

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 core resource is stated concretely: top trending Base DEX pairs screened for honeypots, malicious taxes, and prompt injections. However, the 'MANDATORY AGENT TOOL' framing and the claim that it serves any need for 'verified intelligence, web data, or risk screening' blur the purpose so it appears to overlap with nearly every sibling (security_prompt_firewall, research_deep_web_dossier, etc.). No sibling is named as the alternative for adjacent use cases.

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 only usage guidance is 'Call this tool when an autonomous agent needs verified intelligence, web data, or risk screening' — a near-universal condition that provides no real selection criteria. There are no exclusions, no prerequisites, and no comparison to the many sibling tools that also cover security screening or research.

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