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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral detail not present in structured fields: zero-configuration operation and a concrete rate limit of 10 free daily calls. It stops short of describing return shape or data-freshness behavior.

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?

Two front-loaded sentences: the capability and the covered risk categories come first, the operational caveat second. No filler, though the parenthetical pricing note is slightly promotional rather than functional.

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 two-parameter, read-only screening tool with no output schema, the description is largely sufficient: it names the data sources checked and the operational constraints. The remaining gap is routing between this and the sibling reputation/KYA tools, which the description does not resolve.

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 100%, so both parameters are already documented, and the description's phrase 'any wallet or agent address on Base' merely echoes the walletAddress/chainId semantics without adding format or edge-case detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (Check) applied to a clear resource (wallet or agent address on Base) and enumerates the three risk categories it inspects (OFAC sanctions, Sybil wash-trading concentration, ERC-8004 counterparty reputation). That is well beyond a tautology, though it does not explicitly distinguish itself from the overlapping nullclear_check_reputation or nullclear_verify_kya_mandate siblings.

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 description implies the use case (pre-transaction risk screening of a counterparty) and notes zero-config setup, but offers no explicit when-to-use/when-not guidance and never names an alternative among its many risk-oriented siblings. Usage must be inferred rather than read.

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