nullclear_token_security_audit

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description's real contribution is the quota and setup context: 'zero configuration (10 free daily calls included)', which tells the agent about a rate/usage ceiling that is not in any structured field. It stops short of saying what happens when the free quota is exhausted or how errors surface.

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 capability and its checks, followed by the setup/quota note. Nothing is padded, though the 'Works out-of-the-box' phrasing is slightly promotional relative to the quota fact it conveys.

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 single-parameter read-only tool with no output schema, the description covers the input domain, the checks performed (which doubles as an indication of what comes back), and the quota model. Missing is any hint of the response shape or severity/verdict semantics, which matters for a security audit tool whose value is a pass/fail judgment.

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% and there is only one parameter, so the schema already explains the address format and even supplies a USDC example. The description adds only the chain constraint ('Base ERC-20'), which the schema implies anyway — baseline 3 is 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?

States a specific verb ('Audit') and resource ('any Base ERC-20 token address') and enumerates the checks performed: honeypots, buy/sell taxes, verified bytecode, x402 compatibility. It does not, however, distinguish itself from the sibling scan_token_forensics, which sounds like an overlapping capability, so an agent cannot route between them on description alone.

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?

Usage is only implied by 'Audit any Base ERC-20 token address' — the reader infers this is the pre-trade safety check for Base tokens. There is no explicit when-to-use/when-not statement and no named alternative, despite several plausible siblings (scan_token_forensics, nullclear_wallet_risk_score, nullclear_check_reputation).

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