Search prediction markets across all venues

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

Annotations indicate readOnlyHint=true and destructiveHint=false, and the description adds context like 'Free public search', 'No API key required', and explains that blocked markets remain visible but cannot drive paper opens or alerts. No contradiction 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 somewhat long but well-structured, front-loaded with the core purpose and key differentiators. Every sentence adds value, though it could be slightly more concise without losing information.

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 complexity (11 venues, many returned fields) and the presence of an output schema, the description explains important output fields (referenceProbability, quality, crossPlatform) and clarifies limitations (blocked markets visible but not actionable). This provides a complete understanding for the agent.

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 baseline is 3. The description does not add significant detail about input parameters beyond what the schema provides, but it does mention the source venue list which aligns with the 'source' parameter.

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 it is a 'Free public search over prediction-market events across ALL 11 venues', lists the venues, and explicitly contrasts with the sibling tool 'discover_pm_markets' which is scoped to paper-tradeable venues. The verb 'Search' and resource 'prediction-market events' are specific.

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 'Research/data only: to trade, use discover_pm_markets + pm_quote instead. No API key required.' This provides clear when-to-use and when-not-to-use guidance, including an alternative workflow.

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