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

No annotations provided, so description carries full burden. It discloses the filtering logic (loss-forensics calibrated, blocked categories), output fields, and premium cost. It does not explicitly state read-only behavior but the context of 'signals' implies information retrieval.

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?

Description is four sentences, front-loaded with key purpose. Each sentence adds value; could be slightly shorter but remains informative without redundancy.

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 3 parameters, no output schema, the description adequately explains output structure (row fields) and additional context like premium and blocked categories. No critical information is missing for a data retrieval 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?

Schema coverage is 100% with good descriptions for each parameter. Description adds extra context by listing specific blocked categories (nba/nhl/mlb/ufc/cs2_intraday/la_liga_singlematch), enhancing understanding beyond schema.

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 it returns live copy-trading signals from Polymarket, filtered by trader watchlist and category-quality engine. It specifies BUY signals with blocked categories excluded, and distinguishes it from sibling tools like polymarket_top_traders and polymarket_edge.

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?

Description indicates usage for retrieving bot-grade signals, with a premium cost and note against casual lookup. It implies when to use but does not explicitly list alternatives or when not to use, though the specialized nature makes it clear.

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