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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is fully covered by structured data. The description adds some behavioral value by describing the analysis it performs (skill scoring, lean, agreement with odds) and the disclaimer, but says nothing about data freshness, latency, or limits. With annotations carrying the safety load, a 3 is appropriate.

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 front-loaded sentences that enumerate output content, followed by an accepted-input note and a brief disclaimer. It is efficient overall, though the parenthetical skill list ('edge, win rate, ROI') is slightly listy and duplicated by the output schema.

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 single-parameter, read-only, idempotent tool with a full output schema, the description covers what the tool returns and what it accepts. It need not explain the return shape since an output schema exists, and nothing essential for correct invocation is missing; only cross-sibling disambiguation is absent.

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% for the single 'market' parameter, and the description's 'Accepts a market link, slug or condition ID' merely restates the schema's own description. No format examples, validation rules, or failure behavior are added beyond the structured field. Baseline 3 applies when the schema does the heavy lifting.

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 states a clear resource (Polymarket smart money for one market) and enumerates the specific output (biggest holders per side, scored for edge/win rate/ROI). It is specific and concrete, but it does not differentiate itself from closely named siblings such as get_skilled_whale_trades, get_whale_trades, or get_wallet_scorecard, which an agent could easily confuse it with.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The closest thing to usage context is 'for one market', which implies scoping but does not tell the agent how to choose this tool over the whale-trade siblings. The final disclaimer ('Data, not investment advice') is not usage guidance.

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