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

Annotations already declare read-only, idempotent, non-destructive, but the description adds the traits that actually matter here: a $0.01 USDC charge on Base via x402, a free initial 402 handshake, and no charge on failed checks. It also discloses the informational/not-financial-advice posture, which annotations cannot express.

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?

Information-dense and front-loaded with the core purpose before the return fields, chains and payment mechanics. Minor waste: the price is stated twice ('$0.01 USDC on Base via x402' and 'Price: $0.01 per token'), and the opening alias list is a touch repetitive.

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?

With no output schema, the description compensates fully by enumerating verdict, risk_score, confidence, reasons, simulated buy/transfer/sell honeypot test, tax percentages, mint/blacklist/pause flags, liquidity and concentration. Payment prerequisites and the idempotency/charging behavior are also covered, leaving nothing an agent needs 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 description coverage is 100%, so the baseline is 3, but the description adds the supported chain list with Base as default and documents the alternative payment channel via _meta["x402/payment"] that mirrors the x402_payment parameter. That is meaningfully more than the schema alone conveys.

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+resource with multiple recognized aliases (honeypot detector, rug pull check, scam token scanner) and names the exact input domain (ERC-20 contract or Solana mint). It also enumerates the verdict shape and every signal returned, so an agent knows precisely what it gets back without opening a schema.

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?

It gives operational context for invocation (first call returns PaymentRequired, retry with payment in _meta) and lists supported chains, but never says when to choose this over the closely overlapping siblings erc20_token_quick_scan or token_safety_check_demo. Usage is implied by the name and feature list rather than explicitly routed.

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