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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety bar is covered. The description adds genuinely useful operational context beyond the annotations: it runs against a third-party service (NullClear Bazaar), needs zero configuration, and is rate-limited to 10 free daily calls.

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 sentences, front-loaded with the audit action and its check list before the quota detail. The 'Works out-of-the-box with zero configuration' phrasing is mildly promotional but the quota number that follows is actionable, so waste is minimal.

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 one-parameter read-only audit tool with no output schema, the description covers what is checked and the calling constraints, which is sufficient to call it correctly. It stops short of describing the returned report's shape (scores vs. booleans), a small residual gap given no output schema exists.

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?

There is a single parameter with 100% schema description coverage, including a default and a USDC example, so the schema does the heavy lifting. The description's 'any Base ERC-20 token address' adds only a mild scoping constraint (Base chain, ERC-20 contract, not a wallet) that is already largely present in the schema text.

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 (Audit) and resource (Base ERC-20 token address) plus the exact checks performed: honeypot risk, buy/sell taxes, verified bytecode, x402 compatibility. That is enough to distinguish it from wallet-oriented siblings like nullclear_wallet_risk_score, though no sibling is named explicitly.

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 implies the triggering condition (you have a Base ERC-20 token address and want a security read), and the 'zero configuration / 10 free daily calls' note tells the agent it can be called immediately. It never states when NOT to use it or names an alternative tool for related questions (e.g. wallet risk), so guidance stays implicit.

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