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

Annotations only cover the safety profile (readOnly/destructive/openWorld), and the description goes well beyond them: the per-call price ($0.009 USDC via x402), that payment happens inside the call, that x402 clients pay automatically, the possible verdict values, and the failure mode where a trade simulation cannot run and returns "incomplete". This is exactly the kind of behavioral disclosure structured fields cannot provide.

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 purpose and supported chains are front-loaded, but the body is a dense wall of per-chain checks that reads as a feature dump rather than a decision aid. Much of it (individual EVM/Solana flag lists) is informational but costs length without helping the agent select or call the tool.

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 must describe returns — and it does, naming the verdict, a user-ready one-sentence summary, and concrete flags. Combined with the pricing/payment detail, an agent has everything needed to call it correctly.

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 only 50% (chain has an enum/default but no schema description), so the description compensates: it documents chain default = base, the full accepted chain list, and the useful auto-detection rule that a base58 mint is treated as Solana. It adds real meaning beyond the schema, though the syntax-level detail stays minimal.

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: a token security and honeypot check returning a risk grade A–F, plus exactly which chains and token standards (SPL, Token-2022, EVM) are supported. It is very clear what the tool does, but it never distinguishes itself from the many token_* siblings (token_verdict, token_precheck, token_simulate, token_ai_verdict), so an agent cannot tell which of these to pick based on the description alone.

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?

"before buying or accepting it" gives a concrete decision context for invoking the tool, which is stronger than most siblings. However, it names no alternatives and gives no exclusions, so it stops short of the explicit when/when-not routing that earns a 5.

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