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

Annotations already declare the tool read-only, idempotent, and non-destructive, and the description does not contradict those. It adds useful behavioral detail beyond annotations by enumerating the buyer-draining flags, the inclusion of top holders and LP lock status, and the per-call pricing. It stops short of describing edge cases like invalid tokens or chain mismatches, but the safety profile is fully covered by 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?

Three dense sentences front-load the core purpose, then give decision-relevant output details and cost, with no filler or repetition of schema content. The flag list is long but each item is meaningful for security triage, so every part of the description earns its place.

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 tool without an output schema, the description covers what is checked, what output artifacts are included (flags, top holders, LP lock status, verdict), and the operational cost. The main remaining gaps are the absence of explicit verdict value examples and error behavior, but the context is still strong enough for an agent to select and invoke the tool correctly.

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 already documents chain via a 17-value enum with a default and token via a strict address pattern. The description adds that the target is an ERC-20 contract on supported EVM chains, which helps frame the token parameter, but it does not meaningfully explain the relationship between token and chain or add per-parameter semantics beyond the schema. With 50% schema description coverage, the description only partially compensates.

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 opens with a concrete verb-object pair ('Honeypot and scam check for any ERC-20') and then lists specific risk dimensions such as buy/sell tax, mint, pause, blacklist, and LP lock. It also names the upstream data source, GoPlus Security, and the 'plain verdict' feature, making the tool's purpose unambiguous and distinguishable from generic ERC-20 or price tools.

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 clearly frames when this tool is relevant: security/honeypot analysis for any ERC-20 on supported EVM chains. It does not explicitly contrast with sibling tools like token_risk or erc20_info, so there is no when-not-to-use guidance, but the intended use context is strong and unmistakable.

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