Batch Solana rug/honeypot scan (up to 10 mints)

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

No annotations are provided, so the description carries the full burden. It discloses that it is a paid call and outlines the output: per-token honeypot verdict with risk score, flags, and sellability. It does not cover other behavioral aspects like rate limits, authentication, or error 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?

The description is two sentences long, front-loading the action and key details (batch size, cost, output). Every part adds value, and there is no redundant information.

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 batch scan tool with a single parameter and no output schema, the description covers the primary purpose, batch limit, cost advantage, and output summary. It could potentially mention validation of mint addresses, but overall it is sufficiently complete.

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?

The schema describes the 'mints' array parameter with min and max items. The description does not add additional meaning beyond '1-10 Solana SPL token mints to scan.' Since schema coverage is 100%, the baseline of 3 is appropriate.

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 clearly states the tool scans up to 10 Solana token mints in one call, providing per-token honeypot verdicts (risk score, flags, sellability). It distinguishes itself from individual scan tools like 'scan_honeypot' by emphasizing batch processing and cost savings.

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 description explicitly states ideal use cases: 'vetting a watchlist or a set of launch candidates at once.' It also mentions the cost ($0.10) and the advantage over individual scans. However, it does not specify when NOT to use it or provide direct comparisons to sibling tools.

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