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

With no annotations, the description carries the burden well: it discloses the external data source, the cost model ($0.01 USDC per call, paid via x402 on Base), the enumerated verdict vocabulary, and the returned fields including reasons and 24h buys/sells. It stops short of covering failure behavior (unsupported token, what triggers 'unknown', payment failure handling).

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-loaded with the actionable question, then details, then invocation and pricing. Dense but earned; the semicolon-separated trap lists are compact. Slightly list-heavy in the middle, but no sentence is filler.

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 2-parameter tool with no annotations and no output schema, the description enumerates the return fields and the cost/payment model, so an agent knows what it gets and what it pays. Minor incompleteness around error/edge-case behavior and the meaning of the 'unknown' verdict.

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 description coverage is 100%, so the baseline is 3. The description adds only modest value beyond the schema — confirming chain=base|solana, that token may be a Base address or Solana mint, and the implicit 0x default — without adding format or validation nuance.

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?

Opens with the concrete question it answers ('Can I sell this token?') and names the mechanism (live buy/sell simulation, honeypot.is) plus the exact chain-specific risk checks covered (blacklist, trading switch, freeze authority, permanent delegate). An agent can distinguish this from tokenrisk_check, tokenrisk_verdict, and tokenrisk_token_tax purely from this text.

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 clear: supply an address or mint, optionally specify chain=base|solana, and it returns a sellability verdict. It does not, however, explicitly route the agent away from the multiple tokenrisk_* siblings or say when a cheaper alternative (e.g. tokenrisk_verdict_lite) suffices, which is the main gap given the crowded sibling set.

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