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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety/behavior profile is covered. The description usefully adds that output shape varies by chain family, but it says nothing about rate limits, latency, caching, or whether unlabeled/new wallets return errors versus empty results.

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 short sentences, purpose front-loaded in the first clause, with the output detail compressed into parallel EVM/Solana fragments. No filler and nothing buried.

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 full schema coverage, an output schema, and annotations covering the safety profile, the description is nearly sufficient for correct invocation. The remaining hole is sibling disambiguation, which is the one thing an agent most needs given the dense wallet.* cluster.

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% and the chain enum with its inline EVM/non-EVM grouping is documented in the schema itself; the description only loosely echoes this with "EVM:" and "Solana:". Baseline 3 applies since the schema does the heavy lifting and the description adds no address-format or default-chain detail.

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 gives a specific verb+resource ("Profile a wallet address") and enumerates the actual outputs per chain family (ETH balance, token count, activity labels; SOL balance, SPL holdings, classification). That is far more than a restatement of the name. It stops short of 5 because it never distinguishes itself from close siblings like wallet.portfolio, wallet.labels, or wallet.report, which an agent could easily confuse with this.

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, when-not-to-use, or alternative routing guidance at all. An agent deciding between wallet.profile, wallet.portfolio, and wallet.report gets nothing from the text. The chain-specific output sketch implies context but does not state selection conditions.

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