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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the output fields and the cost, but it does not mention authentication, rate limits, pagination, data freshness, failure modes, or how payment_signature is used to settle the price.

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 description is two tight sentences with no filler. The core purpose is front-loaded, followed by useful output details and pricing.

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 be more complete than this. It provides a few return fields and pricing but omits parameter semantics, usage guidance, payment behavior, and any contrast with sibling tools, leaving too much for the agent to infer.

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 must explain all five parameters. It only semantically explains address and token; chain, blocks, and payment_signature are left unexplained. The 'first and last block seen' output hints at block-awareness but does not clarify the blocks parameter.

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 scope (one address, one token) and the computed outputs (transfers in/out, counterparties, first and last block seen). It lacks an explicit verb but is specific enough to distinguish this from sibling tools like pool_risk or token_report.

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 guidance about when to use wallet_profile instead of alternatives such as token_report or contract_dd, and no mention of exclusions, prerequisites, or appropriate use cases. The scope statement is the only implicit hint.

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