kalshi_market_search

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

While there are no annotations, the description includes the crucial context that the markets are 'CFTC-regulated.' This adds a layer of compliance and risk context that goes beyond standard API functionality. However, it lacks operational details like rate limits or specific error behavior that would constitute full 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 a single, highly efficient sentence that front-loads the core action ('Searches') followed immediately by the complete list of filtering mechanisms. There is zero wasted language.

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?

The definition is complete for a simple search tool, clearly outlining the resource being searched and all available filters. It provides all the necessary information for an agent to determine if and how to call the tool based on a user request.

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?

Although the schema coverage is 100%, the description adds semantic value by explicitly listing the specific categories (Economics, Politics, Financials, etc.) and noting the ability to search by 'keywords,' providing richer context for the `query` and `category` parameters than the schema alone.

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 its function is to search Kalshi prediction markets. Furthermore, by focusing on search criteria (keywords, category, status), it distinguishes itself from sibling tools like 'kalshi_orderbook' or 'kalshi_fee_calculator' which handle specific market interactions.

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?

It provides clear guidance on the inputs and types of data available for filtering (keywords, the six specific categories, and status). It implicitly guides usage by listing these specific options, ensuring the agent knows the boundaries of the search functionality.

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