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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds that the result is a 'saved unbundle report' (implying pre-existing stored output rather than live computation) and enumerates the fields returned. It does not state what happens when no report exists yet for an address or whether one is generated on demand, which is the main residual behavioral question.

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 sentences: a front-loaded question defining the check, then a compact enumeration of the returned report contents. Nothing is redundant, though the question-style opening is slightly rhetorical where a declarative 'Checks whether…' would be tighter.

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 carries the return-value burden and does so reasonably: likely vs. strong links, rationale, funding origin, and an evidence link. The notable gap is the empty/missing-report case and whether the call is purely retrieval, which matters for an agent deciding whether a single call is enough.

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?

There is a single required parameter with 100% schema description coverage ('Solana wallet address'), so the schema already does the work. The description only adds that the address may belong to a KOL or trader being copied, which is marginal meaning beyond the schema and does not touch format, chain variants, or validation.

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?

Names a specific resource (a Solana wallet) and a specific check (hidden side / linked wallets), and even enumerates the report contents the tool returns. It does not explicitly contrast itself with the siblings check_coin or list_research, but the verb+resource phrasing is unambiguous enough that an agent can tell what it does without opening the schema.

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?

The parenthetical 'for example a KOL or trader you copy' gives a concrete usage context that tells the agent when this investigation is appropriate. It stops short of exclusions or naming an alternative path (e.g., when to use check_coin or list_research instead), so it is clear context without routing rules.

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