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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds material context they cannot carry: $0.04 per call over x402 on Base, an x-credit-token prepaid header for unlimited calls, no free tier, and no API key required. Cost and auth requirements are exactly the behavioral facts an agent needs before invoking.

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 in the opening clause and every subsequent sentence adds a distinct fact (mechanism, capabilities, cost, auth). It is somewhat dense and em-dash-heavy, with pricing information wedged mid-paragraph rather than separated, but there is little outright waste.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. Between the mechanism, the danger-level output, the required input, and the cost/auth model, an agent has everything needed to select and invoke it correctly.

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, and the schema already marks it required. The description's 'Required input: address' restates structured data without adding format or syntax meaning, 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: it combines security flags with verified ABI function names and uses AI to explain a contract's dangerous capabilities (mint, pause, blacklist, upgrade, self-destruct) with a danger level. The contrast with 'raw flags' hints at its niche, but it never names the many closely related siblings (contract_danger, owner_powers, token_risk, rug_score), so an agent must infer the boundary itself.

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?

'Goes beyond raw flags to read what the contract can actually do' implies when to prefer this over raw-flag tools, and the pricing/auth notes tell the caller how it can be invoked. However, no alternative tool is named and there are no explicit when-not conditions, so the routing guidance remains implicit.

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