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

With no annotations, the description carries the full burden and does well: it discloses cost, a rate limit (3/day/IP), that the operation is read-only with no transaction sent, and the 402 payment-then-retry protocol. It stops short of describing output format or failure modes beyond the 402 path, so not a perfect 5.

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?

Dense but front-loaded: cost and trial terms lead, followed by what the scan does and the payment retry mechanics. Every sentence earns its place, and the alias note is correctly parenthetical.

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?

No output schema exists, so the description compensates by naming the return contents (risk score, verdict, capability flags). Payment flow, safety profile, and alias are all covered, leaving nothing an agent needs before calling it.

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 already 100%, so the baseline is 3. The description adds real meaning beyond the schema by explaining the payment parameter's role — the tx hash used to retry after a 402 — and constraining the address to a Base token contract.

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 ('Bytecode security scan of a Base token contract') and enumerates what it inspects (honeypot opcodes, mint/blacklist/pause/tax capabilities, risk score, verdict). This distinguishes it clearly from siblings like approval_risk and liquidity_risk. It also flags the security_scan alias, helping an agent reconcile the name.

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?

Gives operational invocation guidance (free trial 3/day/IP, or pay 0.001 USDC; on 402 pay accepts[] terms then retry), which is genuinely useful. However, it never states when to prefer this tool over approval_risk or liquidity_risk, nor any exclusions. Usage is implied rather than differentiated.

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