traders.discover

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

No annotations provided, so description must convey all behavior. Mentions pagination via pages parameter and side effect of auto_watch, but does not state it is read-only, lacks rate limit info, or how ranking is sorted. Adequate but could be more explicit.

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 focused sentences. First sentence states purpose and ranking. Second explains output and suggests a follow-up action. No unnecessary words.

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?

Given multiple sibling trader tools, description adequately covers purpose, output fields, and auto_watch usage. Lacks detail on output structure (no output schema) but mentions key fields. Sufficient for a discovery tool.

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?

Input schema has 100% parameter descriptions. Description adds reinforcement for auto_watch but minimal extra value beyond schema. Baseline 3 is appropriate.

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?

Description clearly states verb 'Fetch', resource 'top traders from Polymarket leaderboard', and ranking criteria (PnL, volume, ROI). Differentiates from sibling tools like traders.analyze and traders.backtest by focusing on discovery for copying.

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?

Explicitly states use case: 'find profitable traders worth copying' and suggests using auto_watch to add to watchlist. However, doesn't mention when not to use or compare to alternatives like traders.score.

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