List Kalshi markets

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is largely covered. The description adds value beyond them by noting it 'Reads the live Kalshi API' (live external data) and by surfacing the cross-tool path to trading, though the 'read-only and places no trade' line largely restates the annotations.

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?

Purpose is front-loaded and the text is short and scannable. The 'this tool is read-only and places no trade' clause is mild redundancy against the annotations, preventing a 5.

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?

With an output schema present, return values need no explanation; parameters are fully documented in the schema and safety is covered by annotations. The description supplies the remaining context an agent needs: live-API behavior and the trading handoff.

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 100%, so the schema already documents limit, status, event_ticker, and series_ticker with defaults and ranges. The description adds no filter syntax or format detail beyond what the schema provides, so the baseline 3 is appropriate.

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?

States a specific verb+resource ('List Kalshi markets for discovery') and explicitly differentiates the sibling set: it names search_markets and list_markets as the Polymarket counterparts, so an agent can route between the two exchanges without opening schemas. The plural 'markets' plus 'for discovery' distinguishes it from the singular kalshi_market detail tools.

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?

Explicit when-to-use (discovery/listing) and a concrete handoff for the trading case: pass 'kalshi:<TICKER>' as slug_or_id to buy, sell, or place_limit_order. It also states the alternative for the other venue ('Use search_markets or list_markets for Polymarket instead'), covering both the when and the when-not.

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