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

Annotations already establish the operation is read-only and non-destructive, and the description adds substantial operational detail: simulated buy/sell honeypot check, owner/proxy/mint/blacklist/pause/fee checks, liquidity, LP burn, buy tax, flow, and verdict categories. No contradiction with 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?

One dense sentence front-loads the purpose and then lists checks efficiently; every listed item is informative. It is longer than necessary but the list is a compact way to convey a broad analysis.

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?

With no output schema, the description compensates by enumerating the checks and giving the verdict values. It does not specify exact output field names or structure, but it is sufficient for an agent to understand what will be returned.

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 50%; address semantics are already provided in the schema. The description names the supported chains and the default, but this mostly restates the chain enum/default rather than adding new meaning.

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 purpose (pre-purchase due diligence on an ERC-20) and a distinctive deliverable (a risk verdict plus a detailed list of checks). This clearly differentiates it from siblings like analyze_token and pre_trade_check.

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 phrase 'Due diligence before buying any ERC-20' gives a clear trigger for use, and the note about Base being the default clarifies scope. It does not explicitly name alternatives or when-not-to-use, so it falls short of a 5.

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