search_polymarket

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

The description implies a read-only operation ('Search... Returns...') but does not explicitly state it is non-destructive or safe. Given no annotations, a slightly more explicit statement (e.g., 'Read-only search') would improve transparency.

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 two short sentences, front-loaded with the core action and input, followed by output and usage guidance. No wasted words.

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?

Lacking an output schema, the description provides a useful summary of return fields (events, markets, odds, volume) and the tool's role. It does not explain what a slug is or how to use it with siblings, but such details are reasonable to omit for brevity.

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?

Both parameters are already well-documented in the input schema (query with examples, limit with defaults). The description adds no additional meaning beyond stating the output's purpose (find slugs), which is only marginally helpful for parameter understanding.

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 markets by keyword, returns matching events with markets, odds, and volume. It explicitly mentions the purpose of finding slugs for other tools, which differentiates it from sibling tools that require specific identifiers.

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 explicitly tells when to use this tool: 'Use this to find slugs for other tools.' This is clear guidance on its role in the workflow, implying it is the entry point for discovering markets, while siblings likely require pre-existing slugs.

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