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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without the description's help. The description adds genuinely new context by revealing the dual data source (fomo or pump.fun) and the breadth of computed fields, which hints at the payload size. It says nothing about behavior for an unknown or delisted handle, handle normalization, or data freshness, so it stops at adequate.

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?

One dense sentence with no filler or hedging, and the core identity (trader profile, which platforms) is front-loaded ahead of the field list. The long comma-separated inventory of return fields is information the agent actually needs to judge relevance, though it reads as a dump and could be grouped more structurally.

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 must carry the return-value burden, and it does so thoroughly by naming the metrics, social counts, positions, and recent trades. For a one-parameter read tool whose annotations cover safety, the remaining gap is minor: no note on what a missing or unknown trader yields. It is otherwise complete enough to call correctly.

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 at 100% schema description coverage, and the schema already explains that the handle should be passed as search or another tool returned it. The description contributes no additional meaning about handle format, casing, or platform prefixes. Baseline 3 is the correct landing point when the schema does all the work and the description only enumerates outputs.

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 resource (a copy.top trader profile on fomo or pump.fun) and enumerates exactly what the profile contains — pnl 30d, roi, win rate, badges, followers, open positions, latest trades. That is far more specific than a restated name and clearly separates it from get_token, get_theses, or get_leaderboard. It loses a point only because it is a verbless noun phrase and never explicitly contrasts itself with a sibling.

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 or when-not-to-use guidance at all: nothing tells the agent to prefer this over get_leaderboard for ranking traders or over get_theses for written analysis. The only routing hint ('as search or another tool gave it') lives in the parameter schema, not the description. Use case is implied by the noun phrase but never stated.

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