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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only risk check but does not state whether it is read-only, what external calls or rate limits exist, or what the response looks like. The lone behavioral clue is the word 'check' and the exclusion of 'ghost ping.'

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?

Two short sentences with zero waste, and the primary purpose is front-loaded before the exclusion. Every phrase earns its place by either stating the action or routing away from a sibling.

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 2-parameter read-only check with no output schema, the description tells the agent what it does and when to use it, but omits return-value behavior and any safety/rate-limit context. It is minimally adequate but leaves important behavioral gaps for an agent to infer.

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% for both parameters (chain and address), so the schema already documents them fully. The description adds no parameter syntax, defaults, or format details beyond what the schema provides, making the baseline 3 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 states a specific check ('honeypot / token-risk check') for ERC20 buying/approving, which distinguishes it from the x402-related siblings by explicitly saying 'Not an x402 ghost ping.' However, it does not distinguish itself from listing_check_before_pay or messari_gate_before_pay, so sibling differentiation is only partial.

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 gives clear usage context ('Before buying or approving an ERC20') and an exclusion ('Not an x402 ghost ping'), which helps the agent avoid the wrong sibling. It stops short of naming the correct alternative tool for the excluded use case, so it is not fully prescriptive.

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