Hidden Gems

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the safety profile is handled. The description adds that results are filtered by minimum win rate, PnL, and trade count, which is useful, but it does not describe sorting, result shape, or the maxTrades-based whale exclusion beyond what the schema already provides.

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 compact and front-loaded with the core purpose. The third sentence, 'These are skilled traders that most platforms don't surface,' is largely redundant with 'underrated' and 'fly under the radar,' which prevents a perfect score.

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 read-only discovery tool with rich annotations and a fully documented parameter set, the description plus schema is nearly sufficient to invoke correctly. The only meaningful gap is that the contents and ranking of the returned trader list are not described, though useToonFormat hints at the output format and no output schema exists to demand more.

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%, so all six parameters are already documented. The description only paraphrases minWinRate, minPnl, and minTrades, and does not add meaning for limit, maxTrades, or useToonFormat beyond what the schema states. Baseline 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 names a specific verb ('Discover') and a specific resource ('underrated high-performing traders') with a clear differentiation angle: 'fly under the radar' and 'most platforms don't surface.' It also states the key filtering dimensions (win rate, PnL, trade count), making it distinct from generic leaderboard or top-trader tools.

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 intended use case—finding capable but non-mainstream traders—is clearly stated through phrases like 'underrated' and 'most platforms don't surface.' It does not explicitly name alternative sibling tools or state when not to use it, so it stops short of full routing guidance.

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