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

Annotations only declare readOnly/openWorld; the description adds substantial context they don't cover: per-call pricing ($0.002 USDC via x402 on Base/Solana/Arc), the fact that failed calls are free, and the caveat that simulation outcomes can drift with pool state. This is exactly the kind of behavioral detail an agent needs before paying for a call.

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 core purpose and output list are front-loaded, and the pricing/EVM caveats follow in order of importance. It is dense but every clause carries information; the output enumeration is slightly long given an output schema exists.

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?

Covers what it does, the chain scope, cost model, and reliability caveats. With an output schema handling return values and a fully documented 2-param schema, nothing material is missing for correct invocation.

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%, with both `address` and `chainId` fully documented including the default of 1 and the 0x+40-hex format. The description adds no further parameter semantics beyond reiterating the EVM-only constraint, so 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+resource ('EVM token honeypot check from honeypot.is') and enumerates the exact outputs (buy/sell simulation, verdict, taxes, risk flags, open-source status, DEX pair liquidity). An agent can immediately distinguish this from siblings like crypto_smart_contract_verify or crypto_token_holder_concentration.

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?

Explicitly scopes the tool to EVM ('no Solana') and warns that simulation results vary with pool state, which frames appropriate use. It stops short of naming which sibling to use instead for non-EVM tokens or for contract-level verification, so no explicit alternative routing.

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