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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, and an output schema exists, so the description's remaining job is small. It does add genuinely non-schema context — a fixed 0.010 USDC cost on Base and Solana Mainnet — which an agent should know before invoking, but says nothing about latency, failure modes, or coverage limits beyond 'instant'.

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?

Two short sentences, front-loaded with the capability and followed by the pricing/chains qualifier. 'Instant' and the audience framing are mild marketing filler but occupy minimal space.

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 single-param read-only check with a full output schema and annotations, the essential facts are covered. The gap is guidance on when this tool belongs in a screening workflow relative to the many sibling audit tools, plus any statement about what a positive honeypot result means.

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% and the single parameter's description already explains the ERC-20 vs Solana SPL address formats. The description's mention of 'Base & Solana Mainnet' loosely corroborates the supported chains but adds no new semantics for token_address; baseline 3 applies.

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?

States a specific verb pair and resource: honeypot verification and transfer fee detection on a token. This is distinguishable from sibling tools like analyze_liquidity or holder_cluster_map, though it never explicitly names those alternatives to sharpen the boundary.

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 only usage signal is the audience phrase 'for autonomous AI trading agents,' which implies a pre-trade safety gate but never says when to call this versus rugshield_pre_swap_scan or rugshield_audit_swap_simulation_proof. No exclusions, prerequisites, or alternative routing are given.

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