Honeypot simulation (EVM)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety. The description adds behavioral context beyond these: it describes the simulation nature (not a real transaction), the meaning of empty results, and the effect of verbose=true (adds top holders and raw payload). This fully discloses behavior without contradicting annotations.

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 information-dense but each sentence contributes value. It front-loads the core purpose, then provides chain details, a routing note, and verbose behavior. It is slightly redundant (aliases are repeated in schema), but remains well-structured and avoids fluff.

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?

The tool is complex (multiple chains, external service, optional verbose), and the description covers all necessary aspects: purpose, supported inputs, routing to alternatives, edge-case behavior (no pair), and output enhancement. An output schema exists, so return structure is covered elsewhere. Nothing an agent needs to call it correctly is missing.

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 parameters are already documented. The description adds extra semantic value by explaining that verbose=true includes top holders with supply percentages and raw payload, and by reiterating the chain aliases in a readable format. It goes beyond the schema's minimal descriptions, though some duplication exists.

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 simulates a buy and sell of an EVM token via honeypot.is and enumerates the specific metrics it reports (is_honeypot, taxes, gas, risk flags, etc.). It names the exact resource and action, and differentiates from sibling rugcheck_report by explicitly directing Solana usage there.

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 explicitly states supported chains (ethereum, bsc, base) with aliases and instructs to use rugcheck_report for Solana, providing clear routing. It also clarifies that a null result means no simulated pair exists, which guides interpretation of the tool's output.

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