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

Goes well beyond the annotations (readOnly, idempotent, openWorld, non-destructive) by disclosing the payment model: $0.08 per call over x402 on Base, a prepaid x-credit-token header for unlimited calls, 1 free call/day, and no API key required. It also states the shape of the result (score, risk level, top signals, riskiest-first ordering), which is exactly the auth/cost context an agent needs before invoking a paid tool.

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?

Front-loads the core capability and keeps cost/auth details compact at the end. The opening two clauses ('Rug-score up to 10 tokens in one call — Screen up to 10 Base tokens in a single paid call') restate the same idea and could be merged, which is the only real waste.

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-value detail is not required, and the description still covers the essentials: scope, chain, batch limit, cost, payment/auth mechanism, and free-tier limits. Nothing an agent needs to call this correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description only restates 'Required input: addresses' and adds nothing about formatting beyond what the schema already says (comma-separated, up to 10).

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+resource ('Rug-score up to 10 tokens in one call'), names the chain (Base), the batch limit (10), and the payload (0-100 rug-probability score, risk level, top signals, sorted riskiest-first). The batch scope plus chain constraint distinguishes it from the single-token rug_score / rug_monitor siblings without needing to open a 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 a clear use case: 'Built for agents triaging a watchlist or portfolio without paying per token,' which tells the agent when this batch tool beats per-token calls. It stops short of naming an alternative (e.g., use rug_score for a single token) or stating exclusions, so it's context without explicit routing.

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