search_markets

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

With no annotations provided, the description must disclose behavioral traits itself. It only says 'Search', which suggests a read-only operation, but does not mention authentication, rate limits, result pagination, or any side effects. The agent cannot infer important behavioral constraints from this text.

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, tightly-worded sentence with no filler. It front-loads the primary purpose. While it is minimal, it is not wordy, and the brevity is appropriate for a simple search operation.

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?

Even with an output schema present, the description leaves the agent without guidance on query semantics, result ordering, or how 'limit' behaves. Given the absence of annotations, the overall tool definition is too thin to ensure correct invocation beyond what the schema already states.

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 0%, so the description must compensate by explaining both parameters. It only rephrases 'query' as 'query string' and says nothing about 'limit', its default, or how the matching behaves. This is insufficient for a tool with two parameters.

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 names a specific verb ('Search'), resource ('Polymarket markets'), and condition ('matching a query string'), clearly stating what the tool does. It does not explicitly differentiate from sibling tools like list_markets, but the query-based focus is enough to infer its role.

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 when to use the tool ('when you have a query string to search markets') and provides context, but it does not mention when not to use it or point to alternatives such as list_markets for browsing all markets. This is acceptable but leaves routing partially to the agent.

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