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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not repeat safety. It adds a summary of the data categories returned but does not disclose extra behavioral traits like rate limits, auth requirements, data freshness, or pagination. This is consistent but not additive beyond the annotations.

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 a single, concise sentence that front-loads the resource ('A wallet:') and lists the key data categories. It is efficient and to the point, though some phrases like 'how those tokens ended' are mildly vague and could be tightened.

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?

For a simple read-only tool with one parameter and no output schema, the description provides a reasonable overview of what the tool returns (age, funder, launches, token outcomes, trading record, holdings). It does not mention any limitations or caveats (e.g., time range, network scope), but the annotations cover safety and the tool is simple enough that this is sufficient.

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 coverage is 100% and the only parameter (address) is already described in the schema as 'The wallet' with a precise pattern. The description does not add any parameter-specific meaning, so the baseline of 3 applies.

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 states the tool's scope: it examines a wallet's history including age, funders, launches, token outcomes, trading record, and holdings. This is specific and distinguishes it from sibling tools like follow_wallet (subscription) and smart_money (top traders), even without naming them.

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?

No explicit guidance is given about when to use this tool versus alternatives. It neither names sibling tools nor states conditions for choosing this over follow_wallet, linked_wallets, or smart_money. The usage is only implied by the description.

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