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

Beyond the readOnly/openWorld annotations, the description discloses genuinely operationally important facts: it is a paid call (3.3 USDC via x402 on Base at a specific POST endpoint), it finishes 'under a minute', and results are explicitly partial. That is strong added value, though a substantial share of the text is identity/fee-disclosure marketing rather than behavior the calling agent needs.

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 screening sentence and the input example are correctly front-loaded, but the definition then runs on through fee set-aside, ERC-8004 registration number, Virtuals ACP link and payout wallet address. Those sentences serve operator credibility more than tool selection and dilute an otherwise tight definition.

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 no output schema, the description compensates by listing the payload contents (flags, liquidity, social evidence, sources, timestamp, CAUTION/ALERT verdict) plus latency and cost. Caveats about partial coverage are present; only the exact structure/format of the verdict field is left implicit.

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% and the schema already documents both parameters including address formats and the chain enum. The description only restates the two field names and adds one example payload, which is marginally useful but not meaningfully beyond the 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 opens with a specific verb and resource ('Screen a token for red flags') and enumerates exactly what the screen returns: risk flags, DEX liquidity, social/web evidence, sources, timestamp and a verdict. It never names or differentiates itself from close siblings such as rug_honeypot_quick_check or contract_security_scan, so an agent must infer which screening tool to pick.

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?

Usage context is stated plainly ('before you touch it') and a clear limitation is given ('Partial automated screen; cannot certify safety or audit status'), which tells the agent this is a pre-trade triage step, not a certification. It gives no explicit when-not conditions or named alternatives among the many screening siblings.

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