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

With no annotations at all, the description carries the full disclosure burden, and it does add real behavioral value by naming the checks performed (honeypot, holder concentration, risk score), which implies read-only on-chain analysis. However, it omits whether results are live or cached, which chains are covered, auth or API-key requirements, and rate limits, leaving meaningful behavioral gaps.

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 compact sentence, front-loaded with the tool's identity followed by the specific checks, with no filler wording. The colon-list format is efficient but flatter than it could be, giving no hierarchy among the four capabilities.

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 annotations, no output schema, and a description that only lists capability areas, an agent cannot tell what the tool actually returns, what the risk score scale is, or how the subject token is specified given that only maxResults is accepted. For a multi-dimensional audit tool, the description is materially under-specified.

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 the single maxResults parameter, so the schema already documents it fully, and the description adds nothing about what is being counted or limited. This is the expected baseline when the schema does the work, with no compensating detail from the prose.

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 enumerates concrete analysis outputs: DEX pair liquidity, holder concentration, honeypot checks, and risk scoring, which tells an agent this is a token due-diligence tool rather than a price or arbitrage tool. It is structured as a label plus a noun-phrase list with no verb, and it offers no explicit differentiation from siblings such as crypto_orderbook_arbitrage_scanner or defi_yield_tvl_stablecoin_monitor.

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?

There is no statement of when to use this tool versus alternatives, no preconditions, and no mention of which chains or token types are supported. The description also never explains how the target token is identified, which is the single most important usage question for a scanner-like tool.

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