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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful output-scope detail (live balances, tier, contract detection), but says nothing about rate limits, masking behavior, or what happens without a key — the paid/unmasked aspect only appears in the schema, not the description.

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?

Two tightly packed sentences with zero filler; the chain scope is front-loaded and the return fields follow. Every clause carries 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 output schema, the description correctly carries the burden of describing return values, and it does so thoroughly (balances, nonce, tier, contract detection). It falls short only on operational context such as masking defaults or rate limits, which would help an agent interpret results.

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 address, x_api_key, and payment_signature parameters are already fully documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 a specific verb (profiler) and resource (multi-chain wallet portfolio) and enumerates exactly what it returns: USDC/native balances, nonce/outgoing tx counts, wallet tier, and contract-vs-EOA detection. It is clearly a wallet-intelligence tool, though it does not explicitly differentiate itself from the sibling whale_alpha_radar.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as whale_alpha_radar or token_due_diligence. The agent is left to infer that this is the tool for a single-address profile rather than an aggregate whale feed.

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