search_markets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds meaningful context by noting the Gamma API source and listing the return fields, plus hints at chaining for deeper data. It lacks details on rate limits, pagination defaults, or error behavior, but for a search tool this is adequate.

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 concise sentences: the first defines the action, the second lists outputs, and the third gives chaining suggestions. It is front-loaded, avoids redundancy, and every sentence earns its place.

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 search tool with no output schema, the description adequately covers return values and provides integration guidance. It could be more complete by stating the exact response structure or default filters, but given the simplicity of the tool, it is sufficiently complete for an agent to select and use it correctly.

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 each parameter is already well-documented. The description adds minimal parameter-specific semantics beyond what the schema states; it merely restates that the query is text search and that CLOB token IDs are included in results, which is useful but not sufficient to exceed the baseline.

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 tool searches Polymarket prediction markets via text query and lists the returned metadata (question, prices, volume, liquidity, CLOB token IDs). However, it does not differentiate this tool from the sibling search_markets_enriched, which likely serves a similar but possibly more detailed purpose.

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?

Provides clear usage context by suggesting chaining with other tools like get_clob_market and get_live_prices, implying this is the initial discovery step. It does not explicitly exclude alternatives or state when not to use this tool, so it falls short of a perfect score.

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