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

With no annotations, the description carries a heavy burden, and it delivers relevant context: authentication/payment requirements, explicit limitation to public onchain behavior, and a detailed overview of returned metrics and event types. It implies a read-only lookup without saying so explicitly, and it does not disclose rate limits or failure 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?

The second sentence is efficient and information-dense. The first sentence, however, front-loads lengthy payment details (bearer token, per-call payment via two protocols, four tokens, chains) before stating what the tool does. No sentence is wasted, but the ordering is suboptimal and the payment section is more verbose than ideal.

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?

An output schema exists, so return values are covered structurally. The description also gives useful authentication guidance, the public-data limitation, and the list of included metrics/events. The main missing context is a precise explanation of how the chain parameter behaves and which sibling tools should be used for broader or different reports.

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 needed to explain the address and chain parameters. It adds only that address is a wallet and that the profile spans chains, but it does not clarify what role the optional chain enum plays, whether omitting it aggregates across all chains, or what address formats are accepted. The description undercompensates for the absent schema-related context.

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 clearly identifies the resource (one wallet address) and the output (risk score, mixer funding, dormancy, transaction count/value, protocols, bridge count, flagged status, and recent events). It does not explicitly distinguish it from sibling reporting tools such as deep_report or situation_report, so it misses some differentiation, but the purpose is unmistakable.

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 intended use is implied: a single-wallet risk check. However, there is no explicit guidance on when to prefer this tool over alternatives, nor any exclusions such as unsupported wallet types or limitations on address formats.

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