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

With no annotations, the description carries the full burden, and it does surprisingly well: it discloses the $0.02 cost, that calls return a payment requirement until supplied with a payment header, bundle_token, or api_key, and that the output is a heuristic. It still omits error behavior for bad addresses and any rate limits or failure modes.

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?

Dense but well front-loaded: the paid cost and purpose lead, followed by outputs, chains, params, and the payment/auth mechanics. Each sentence carries information with little 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?

There is no output schema, so the description usefully describes the return payload (score, verdict, flags), and it explains the payment gating and supported chains. Complete enough to call correctly, with only minor gaps around input validation and rate limits.

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 0% and the schema gives bare titles, but the description compensates by explaining chain examples (base), the address format (0x… or a Solana mint), and the role of payment, bundle_token, and api_key. All five parameters are addressed, though the exact accepted chain strings and key-format expectations remain unstated.

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 states a specific verb and resource ('Rug-check verdict for an on-chain token') and enumerates the concrete outputs (0-100 risk score, verdict, flags for honeypot, mint/freeze authority, taxes, holder concentration, LP lock). This clearly distinguishes it from data-oriented siblings like get_base_wallet_intel or get_whale_flow.

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 is implied by the 'rug-check' framing and the supported chain list, and it helpfully points to get_free_api_key for minting a free-tier key. However, it never states when to prefer this over other safety-adjacent siblings or any exclusions/limits on the heuristic's reliability beyond 'not financial advice'.

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