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

With no annotations, the description carries the full behavioral burden; it does disclose genuinely useful traits — static (non-AI) analysis, deterministic output, fast, and the exact pattern set. However, it says nothing about input expectations (which of the five source params is required), output shape, or failure behavior, leaving large 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?

The purpose is front-loaded and the body is short, but it is a colon-joined run-on of fragments rather than sentences, and the trailing 'Case: minia2a.uk/blog/...' promotional URL does not help invoke the tool and does not earn its place.

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, no annotations, and five undocumented parameters means the description must supply more than it does. It never explains what a caller must provide or what they will get back, so it is incomplete for a tool of this input complexity.

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?

Five parameters (code, source, contract, source_gz, source_b64) exist at 0% schema description coverage, and the description adds zero information about them — no indication of whether they are alternatives, mutually exclusive, or formats (gzip/base64). It provides no compensation for the coverage gap, so an agent cannot know which field to populate.

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 states a specific verb+resource ('Smart contract security audit, solidity vulnerability scan') and enumerates the 11 static patterns checked, so an agent knows exactly what it produces. It does not, however, differentiate itself from near-identical siblings like x402-contract-scan or x402-contract-triage, leaving selection ambiguous.

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?

'Fast pre-check, deterministic' implies a usage context (a quick preliminary scan, not a deep/exhaustive audit), but the description never states when to use this versus x402-contract-scan, x402-contract-triage, or x402-ai-audit. Usage is implied rather than instructed, and no exclusions or prerequisites are given.

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