Search/list active Polymarket prediction markets

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

Annotations already convey safety (readOnlyHint, idempotentHint, openWorldHint). The description adds valuable behavioral traits: ranking by 24h volume, returned fields, cost ($0.003 per call), and the 'active' filter. This goes beyond what annotations provide.

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 a single sentence with a brief pricing note, all front-loaded with the core purpose. No wasted words; every phrase adds value.

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 simple search tool with 2 optional params, no output schema, and strong annotations, the description is fairly complete. It covers output fields, ranking, cost, and active filter. It could mention output format or error handling, but given the tool's simplicity, this is adequate.

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 both parameters described. The description does not add new meaning beyond the schema; it only lists 'question' in the returned fields, which is already clear from the schema's 'q' description. 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 clearly states the action ('Search or list'), the resource ('active Polymarket prediction markets'), and the ranking ('by 24h volume'). It also lists the returned fields, making it distinct from sibling tools like get_polymarket_market (single market) and search_kalshi_markets (different platform).

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 implies usage for searching/listing polymarket markets but does not explicitly differentiate from sibling tools (e.g., when to use this vs. get_polymarket_market). The pricing note is a cost hint, not a usage guideline. No exclusions or alternatives are mentioned.

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