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

Annotations already declare openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds a genuinely useful non-schema detail — the $0.02 USDC per-call cost — but omits return format, latency, or accuracy caveats for a screening result.

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?

A single front-loaded line that wastes no words and puts the resource and scope first. It is terse but every clause carries meaning; the brevity is efficient rather than padded.

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 and zero parameter documentation, the description should explain what a screening result contains (risk score, flags) and clarify the 'chain' input, but it does neither. For a call that costs money, the omission of what is returned is a real gap.

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% and there are two parameters. The description says nothing about 'address' or 'chain' (e.g., accepted chain values, format expectations), so it fails to compensate for the empty schema and leaves 'chain' entirely ambiguous.

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 ('Wallet risk screening') and enumerates concrete checks (OFAC sanctions, scam flags, tx patterns). However, it does not distinguish itself from the sibling 'sanctions-screen', which appears to overlap on the OFAC dimension.

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?

No when-to-use or when-not-to-use guidance. Given overlapping siblings like 'sanctions-screen', 'token-safety', and 'threat-intel', the agent is left to infer whether this or a sibling should be called for a given screening need.

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