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

With no annotations, the description carries the full burden. It discloses the verdict scale (SAFE/RISKY/CRITICAL), the 0-100 score, the combination of STATIC and BEHAVIORAL checks, the blue-chip false-positive guard, and even the pricing and payment method ($0.01 per call, x402, USDC on Base mainnet). It does not explicitly state it's a read-only operation, but the nature of a safety check implies non-destructive behavior. This is a high level of transparency.

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 description is front-loaded with the purpose but contains redundancy: 'rug check and honeypot / scam detection' is repeated as 'scam-token detection', and 'before trading' is repeated as 'Pre-trade'. The pricing and payment sentence is useful but could be separated or abbreviated. It's not a model of conciseness, though it remains readable and informative.

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?

Given there is no output schema, the description explains the main output (verdict SAFE/RISKY/CRITICAL + 0-100 score) and analysis methodology. It also covers pricing and the false-positive guard. It does not detail return fields, error cases, or prerequisites like RPC endpoints, but for an agent deciding to invoke this tool with a mint address, it provides enough context to select and call correctly. The absence of an explicit read-only statement is a minor gap.

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%, so the baseline is 3. The description does not add parameter-specific semantics beyond the schema; the mint example 'EPjFW...Dt1v' (USDC) is already in the schema description. The 'deep' parameter's meaning (more RPC calls) is explained in the schema, and while the description's emphasis on behavioral analysis aligns, it does not add new information. The schema already carries the burden.

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 clearly states the tool's purpose: 'Solana SPL token safety, rug check and honeypot / scam detection before trading' and later 'Pre-trade SPL token security / scam-token detection'. It names a specific verb (safety check, rug check) and resource (Solana SPL token), and distinguishes it from siblings like solana_pre_trade by focusing on rug/honeypot and behavioral detection.

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 provides clear context: 'before trading' and 'Pre-trade' indicate when to use it. It also mentions that it catches 'behavioral rugs static checkers miss', implying it complements static analysis alternatives. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full exclusion guidance.

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