Discover prediction markets

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

Annotations declare readOnlyHint=true and destructiveHint=false. The description adds depth by clarifying that it is 'discovery only', that pm_quote is the eligibility gate, and that it uses mock sources and virtual funds. No contradictions with annotations.

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 three sentences, each serving a distinct purpose: what it does, what it returns, and how to use it in the pipeline. No wasted words, well-structured.

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 discovery tool with 6 optional parameters and an output schema, the description covers the core purpose and integration with sibling tools. It lacks detailed explanation of sort options but is sufficient for effective use.

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 schema already documents all parameters. The description does not add new meaning beyond listing return fields. It is adequate but not exceptional given the high schema coverage.

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 clearly states the verb 'Find' and specifies the resource: active-open, quote-ready-first prediction markets. It distinguishes itself from siblings like pm_quote and open_pm_position by noting it is 'discovery only' and recommending subsequent calls.

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 instructs to call pm_quote with a returned outcomeExternalMarketId before open_pm_position, establishing a clear workflow. It also notes the paper trading context. While it doesn't list exhaustive when-not-to-use scenarios, it provides strong guidance.

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