kalshi_markets_history

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

Mentions 'credential-free public' but no annotations exist. Does not disclose rate limits, behavior for >25 tickers, or whether returns are paginated. Insufficient for a multi-market data tool.

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?

Two sentences front-load key info: batch, candlesticks, up to 25, credential-free. 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?

Lacks output schema, but describes what is returned (candlesticks). Covers constraint (25 tickers) and auth context. Minor gaps: no pagination info or response structure details.

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 has 100% coverage with descriptions. The description adds 'up to 25 market tickers' and 'normalized candlesticks' which provide context beyond schema, but baseline is 3 since schema already documents parameters.

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?

Description clearly states it returns normalized Kalshi candlesticks for batch market history up to 25 tickers. Distinct from siblings like kalshi_market_history (single market) and kalshi_historical_market_history (historical single market).

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?

Usage is implied ('batch' vs 'market' singular) but no explicit guidance on when to choose this over sibling tools like kalshi_market_history or alternatives.

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