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

With no annotations, the description carries the burden well: it discloses the data source (US Treasury SDN list, public data), the cost ($0.01 per call in USDC), the payment mechanism (x402 in params._meta['x402/payment']), a free sample, and the HTTP method/URL. It still omits error/rate-limit behavior and what the response actually 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?

Front-loaded with the core capability, then cost and access mechanics in terse telegraphic form. Dense but efficient; the slash-separated fragments and bare URL are functional rather than wasteful.

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?

Covers what the tool produces, its data source, and its pricing/access model, which are the essentials for invoking it. However, with no output schema, the description should sketch the response shape (profile fields, risk score scale, sanction hit/no-hit verdict) and it does not.

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 the schema already explains the address format and range_blocks bounds. The description adds nothing parameter-specific, and does not clarify how the x402 payment meta interacts with the declared parameters.

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 precisely what the tool returns: a base wallet activity profile, a heuristic risk score, and an exact-address OFAC SDN screen. The only ambiguity is that it advertises two endpoints (/profile and /sanctions), which blurs the boundary with the sibling walletprofile__sanctions tool.

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?

Usage is only implied by the endpoint listing and the 'Free /sample' note; there is no explicit 'use this when...' or guidance on when to prefer walletprofile__sanctions or check_sanctions__* instead. An agent can infer intent but is not routed.

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