Search Polymarket markets

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real semantic context beyond that: price is the implied probability (0-1), not an executable quote, and it directs to the orderbook for tradeable prices. It does not elaborate on pagination or rate limits, keeping it short of a 5.

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?

Front-loaded with purpose and usage, then args and examples. The 'Returns' block largely duplicates the existing output schema and is the one section that does not fully earn its place, but overall structure is tight and scannable.

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 four optional params, 100% schema coverage, and an output schema, the definition covers everything an agent needs: mode selection, slug handoff, price interpretation, and format choice. No material gaps remain.

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%, so the baseline is 3; the description adds value with concrete query examples ('bitcoin', 'election'), the omitted-query fallback behavior, and a worked example ('Fed'), which exceeds the schema's field-level text.

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?

States a specific verb (discover/search) and resource (Polymarket markets), plus the dual mode (keyword search vs. top-by-volume listing). The line 'Use this first to find a market's slug' explicitly positions it against siblings like polymarket_get_market and polymarket_get_orderbook.

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?

Explicit sequencing guidance ('use this first ... then feed the slug into the other tools') and an explicit alternative with its trigger condition ('For an executable price/spread, use polymarket_get_orderbook'). This tells the agent when to use it and when to route elsewhere.

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