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

With zero annotations the description carries the full burden and mostly does: it discloses the data sources (on-chain proxy/owner/bytecode/mint-authority checks plus DEX pool metrics), the cost ($0.008 USDC, x402 on Solana), and the non-advice disclaimer. It omits latency expectations, failure modes on unknown tokens, and whether payment is settled before or after a result is returned.

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?

One dense scoped sentence plus a compact input signature; the scope and output format are front-loaded. The 'Not financial advice' clause is boilerplate but short enough to be tolerable.

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?

For a paid, multi-chain analysis tool with no output schema and no annotations, the description covers purpose, inputs, data sources, and pricing — enough to call it correctly. The remaining gap is response shape and error/empty-data behavior, which nothing else in the structured fields supplies.

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 75%, so the schema already documents free_trial and x402_payment. The description adds one genuinely new fact — that chain is optional and auto-detected — but says nothing about the payment payload flow or when free_trial is honored, leaving the two most operationally tricky parameters to the schema alone.

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 names a specific verb+resource (token verdict) and enumerates the exact output grades (SAFE / CAUTION / RISKY / DANGER) plus the two supported chains. It stops short of differentiating from the sibling solana_token_check, which overlaps on the Solana half of this tool's scope.

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 'fast verdict' framing and the enumerated data sources imply when this tool fits (quick token risk screening), but there is no explicit when-not condition and no sibling is named as the alternative. The paid/free-trial distinction is only explained through the schema, not in the prose.

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