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

Annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds meaningful operationaal context: it combines secarity flags with the ABI, uses Claude to generate an explanation, returns a danger level, costs $0.04 per call on x402/Base, supports a prepaid x-credit-token header, offers a free tier, and requires no wallet or API key. No contradiction with annotations.

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 pricing/auth details are placed at the end, which helps an agent scan quickly. There is a little redundacy in saying both 'what dangerous powers a contract has' and 'explains the contract's dangerous capabilities,' and the required-input line duplicates the schema, but overall the text is dense and mostly worthwhile.

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 tool with an output schema and strong annotations, this description covers the key call-time facts: purpose, input, source data, output nature, danger level, pricing, authentication mechanism, free tier, and account requirements. Nothing needed to invoke it correctly is missing.

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 only one parameter, address, and the schema already describes it as 'Contract address' (100% schema description coverage). The description merely repeats 'Required input: address' and adds no new detail about format, chain, checksumming, or address type, so the baseline score of 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 ressource: it explains a contract's dangerous capabilities by combining secarity flags with the verified ABI names and outputs a danger level. It also distinguishes itself from raw-flag approaches by claiming it 'goes beyond raw flags,' though it does not explicitly name sibling tools like contract_danger or rug_score.

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 context is implied: an agent would call this when it needs a plain-English explanation of what dangerous powers a contract has, rather than raw flags. However, there is no explicit when-to-use, when-not-to-use, or named alternatives among the many risk-related sibling tools, so the agent must infer selection.

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