kalshi_markets

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

With no annotations provided, the description carries the burden. It states the tool is 'credential-free' and uses 'public market-data JSON', indicating read-only access and no authentication needed. However, it does not detail other behavioral traits like pagination behavior, rate limits, or whether results are real-time or cached.

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 sentences long, directly stating the tool's purpose and a key parameter. It is front-loaded with 'Kalshi markets' and contains no superfluous information.

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?

Given the tool's complexity (6 parameters, no output schema, numerous siblings), the description provides concise yet sufficient context for a listing tool. It could benefit from clarifying what 'normalized' means or detailing output fields, but overall it is complete enough for an agent to use.

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?

The input schema has 100% coverage, so baseline is 3. The description adds value by explicitly listing accepted values for the 'status' parameter ('unopened', 'open', 'closed', 'settled'), which is not fully conveyed by the schema's enum description alone. Other parameters are not elaborated.

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 that the tool returns 'normalized Kalshi market rows from credential-free public market-data JSON', which is a specific and distinctive purpose. It differentiates from sibling tools like 'kalshi_market' (singular) and 'kalshi_markets_history' by emphasizing public data and normalization.

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 does not provide explicit guidance on when to use this tool versus alternatives like 'kalshi_market' or 'kalshi_markets_history'. It mentions the status enum values, which implies filtering capability, but lacks direct comparison or context.

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