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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that results are 'batch' and 'candlestick'-shaped; it says nothing about pagination, upstream limitations, or how multiple tickers' candles are returned.

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?

A single six-word fragment with no filler and the key qualifier ('batch') front-loaded. It is efficient, though its terseness borders on under-specification rather than optimal concision.

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?

An output schema exists, so return values need not be explained, and the read-only annotation covers safety. However, for a five-parameter tool spanning time ranges, intervals, and multi-ticker batching, the description provides no context on time-range limits or batching behavior, leaving the agent to rely wholly on the schema.

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 timestamps, period_interval, and include_latest_before_start are already documented in the schema. 'Batch' hints at the market_tickers array and 'candlestick' hints at period_interval, but no syntax, defaults, or constraints are added beyond the schema.

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 phrase 'Kalshi batch market candlestick history' names the resource (Kalshi market candlesticks), the operation (retrieve history), and the scope ('batch', implying multiple tickers). It implicitly distinguishes itself from the singular kalshi_market_history sibling via 'batch', but never names that sibling or states the contrast explicitly.

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?

There is no when-to-use guidance, no mention of alternatives such as kalshi_market_history or kalshi_historical_market_history, and no stated preconditions (e.g. that tickers must be known/valid). The agent must infer the use case entirely.

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