Discover prediction markets

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

No annotations are provided, so the description carries full burden. It discloses read-only behavior implicitly ('discovery', 'returns'), but does not explicitly state 'does not modify state' or mention rate limits. However, the purpose and return fields strongly imply a safe read operation.

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 concise but packs essential info: purpose, return fields, usage flow, and disclaimers. It is front-loaded with the main action. Could be slightly trimmed but is efficient overall.

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 the moderate complexity (5 optional parameters, no output schema), the description adequately covers what the tool returns (source, slug, outcomeExternalMarketId, etc.) and how to use it with sibling tools. It leaves no critical gaps for an agent to correctly invoke it.

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 the parameters are well-documented in the schema. The description does not add extra meaning beyond the schema's field descriptions (e.g., 'Optional search text', 'Source filter'). 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?

The description uses a specific verb ('Find') and resource ('active-open, quote-ready-first prediction markets') with source scope (Kalshi, Polymarket). It clearly distinguishes from sibling tools like pm_quote (which is for quoting) and open_pm_position (which opens positions).

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 description explicitly states when to use this tool ('discovery only') and provides a clear workflow: call pm_quote with the returned outcomeExternalMarketId before open_pm_position. It also clarifies paper trading and non-financial advice, reducing misuse risk.

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