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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful scope (a fixed 7-day trade window, derived signals like skill and insider evidence), but says nothing about behavior for an unknown address, data freshness, or response shape beyond the field list.

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?

A single short sentence with the key scope (one wallet, 7-day trades) front-loaded and no filler. It is terse to the point of being telegraphic, but nothing is wasted.

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 does carry the return-value burden and lists the main categories returned, which is helpful. However, for a single-parameter lookup tool it omits any treatment of the required address input, error cases, or how the trade window is anchored, leaving real gaps.

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% and the description never mentions the sole required 'address' parameter, so the agent gets no meaning beyond the schema's regex pattern. It does implicitly establish that only one wallet is fetched, which is the only semantic added.

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 fragment 'One wallet: skill, early calls, holding habits, insider evidence and its trades of the last 7 days' makes clear this is a single-wallet lookup returning analytics plus recent trades, which separates it from the list-style sibling get_top_wallets. It lacks an explicit verb, but the resource and scope are unambiguous.

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 at all: nothing says when to call this versus get_top_wallets, get_feed, or get_token, nor any prerequisite such as needing a valid address first. The reader must infer usage from the name alone.

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