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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description meaningfully adds on top: it discloses the free-tier throttle (6 scans per 10 minutes) and the exact auth mechanism (X-Api-Key header on the MCP connection). That rate-limit and auth detail is genuinely non-obvious behavioral context not present in the structured fields.

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-loaded with identity and then output contents, scoping, and limits. Every sentence carries information, though the middle sentence listing detection categories is slightly list-heavy.

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 correctly carries the return-value burden by naming the verdict tiers and the flag categories an agent will receive. Combined with chain coverage, rate limits, and auth, an agent has enough to invoke and interpret it; the only real omission is which sibling to prefer.

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 description coverage is 100%, so both parameters are already documented in the schema, including the chain default and the auto-detection of Solana mints. The description adds no syntax or format detail beyond that, so the 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 and resource ('NERON's contract scanner') and enumerates the concrete outputs it produces (verdict, flags, taxes, honeypot simulation, owner powers, liquidity, holders), so an agent knows exactly what it returns. It does not, however, distinguish itself from the overlapping siblings check_token_risk and check_tokens_risk, which is a real ambiguity.

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?

Provides useful operating context – 'Robinhood Chain by default; also Solana and 15 more EVM chains' – and discloses the rate limit and how to lift it, but never says when to choose this tool over check_token_risk or check_tokens_risk. Usage is implied rather than routed.

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