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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new operational context: free tier with a daily per-caller quota, and the fact that payment/auth material travels in MCP headers (X-Payment, X-Payment-Tx, Authorization: Bearer fg_…) rather than in arguments — a real failure mode an agent would otherwise hit.

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 question is front-loaded, but the same content is then restated in Chinese, then re-stated again in [zh]/[en] vendor blocks, tripling the length with no new information. The payment-header note is valuable but buried at the end.

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?

With no output schema, the description usefully enumerates return fields (risk level, is-contract, tx count, USDC balance, confidence) and covers auth/quota constraints. The main remaining gap is chain enumeration and address format, but overall an agent has enough to call 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?

Schema description coverage is 0%, so the description carries the full burden, yet it only says "Args: address, chain" without explaining address format or what values chain accepts. The asset title mentions Base / Ethereum, which hints at valid chains, but that is incidental rather than a stated constraint.

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 opening line frames a specific question ("is this wallet address risky") plus the resource (wallet address) and enumerates the returned facts, so the operation is unambiguous. It does not, however, name the sibling it differs from (address-risk.risk, address-safety.address_report/screen), so an agent must infer that "quick/free" means a lightweight snapshot rather than the fuller checks.

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?

The "free" positioning and the daily per-caller quota imply this is the cheap pre-check before heavier screening tools, which is useful implied guidance. There is no explicit when-to-use vs. when-not statement and no named alternative among the several address-screening siblings.

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