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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, and the description adds genuinely useful operational context the annotations cannot: pricing ($0.04/call over x402 on Base), the prepaid x-credit-token header for unlimited calls, no free tier, and no API key required. It also warns that an unverified contract is itself a red flag, which frames result interpretation. It does not describe latency, rate limits, or failure modes.

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 core capability is front-loaded in the first sentence, and the parenthetical abuse-function list is dense and information-bearing rather than filler. The cost/access sentence is necessary given the paid model. The rhetorical hook and "Diligence a price feed can't give" are light marketing that slightly dilutes an otherwise tight block.

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-address read tool with annotations and an output schema present, the description supplies purpose, the abuse categories flagged, payment mechanics, and required input — nothing an agent needs to call it is missing. The one residual gap is the absence of any routing signal against sibling risk-scan tools.

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?

Only one parameter with 100% schema description coverage, so the schema already carries the contract ("Contract address"). The description restates "Required input: address" without adding format, checksum, or chain-scoping detail. Baseline 3 applies when structured data does the heavy lifting.

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: "Reads a verified contract's ABI and flags owner-callable abuse functions," followed by a concrete taxonomy (mint/pause/blacklist/setFee/withdraw/upgrade). An agent immediately knows the output class. However, it never distinguishes itself from close siblings like owner_powers, ai_contract_risk, or contract_owner, so sibling selection is left to guesswork.

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?

Framing ("What can the owner do to you?", "Diligence a price feed can't give") implies the use case is pre-interaction contract due diligence, and "An unverified contract is itself a red flag" hints at the trigger condition. But there is no explicit when-not guidance and no named alternative among the many overlapping risk tools (owner_powers, rug_score, token_risk), so usage is only implied.

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