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

With no annotations, the description carries the full burden and does well: it discloses pricing ($0.01 USDC), the network (eip155:8453), the payment channel (x402 in params._meta), a free sample path, and the important limitation that screening is exact-address only. It stops short of describing failure modes, rate limits, or what the heuristic risk score contains.

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, with cost and transport details trailing. It is dense but every element earns its place except the redundant endpoint paths '/profile and /sanctions', which add ambiguity rather than information.

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 annotations and no output schema, the description must fully explain behavior, and it covers cost, payment, data source, and screening scope. It does not explain the shape of the risk score, what a sanctions hit returns, or error behavior, which matters for a paid screening call an agent must decide to invoke.

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 coverage is 100%, so address format and range_blocks bounds are already documented. The description adds value beyond the schema by documenting the x402 payment parameter that does not appear in the properties list, which an agent would otherwise miss.

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 description names the resource precisely: wallet activity profile, heuristic risk score, and an exact-address OFAC SDN screen, plus the data source (US Treasury public list). It does not differentiate from the sibling walletprofile__profile, and the '/profile and /sanctions' phrasing leaves it ambiguous whether this tool is a combined endpoint or sanctions-only.

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?

There is no statement of when to use this versus the many sibling screening tools (check_sanctions__address, check_sanctions__screen, check_sanctions__verdict) or versus walletprofile__profile. The only usable cue is 'Free /sample' and the price, which hint at a trial-first workflow but give no explicit guidance.

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