check_honeypot

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

With no annotations, the description carries the full burden and does well: it discloses the execution method (RPC simulation on Base Mainnet), the return content (buy/sell taxes in bps, blacklist flags), and an unusual operational constraint (0.005 USDC cost on Base). It stops short of describing failure modes, latency, or what happens if the simulation times out.

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?

Effectively two sentences plus a cap-style label; every clause carries information (method, output, cost) and the core purpose is front-loaded. Slightly dense in the second sentence but no filler.

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-input onchain simulation tool with no annotations and no output schema, the description covers method, results, and cost adequately. It omits failure behavior and any RPC-dependency caveats, which keeps it from being fully 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?

One parameter with 100% schema description coverage, so the schema already explains token_address fully. The description adds no format, validation, or address-type detail beyond what the schema provides, which is the baseline case for a fully documented single parameter.

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 resource (ERC-20 token on Base) and the exact mechanism (decompiles bytecode and simulates buy/sell execution against Base Mainnet RPC) to answer a concrete question: can the token be sold. The purpose is unmistakable and materially distinct from a liquidity analyzer or a generic pre-swap scan.

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?

Usage is implied rather than stated: an agent can infer this is a pre-trade safety check, but the description never says when to prefer it over rugshield_pre_swap_scan or analyze_liquidity, nor does it state prerequisites or exclusions. The cost line hints at a gating consideration but does not route the agent between siblings.

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