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 nothing behavioral beyond that — no note on rate limits, historical-data availability, default time range, or what happens when start_ts/end_ts are omitted. It restates the return shape but discloses no operating characteristics.

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?

It is a four-word noun fragment, which is concise in size but under-specified rather than efficient. There is no front-loaded verb or scope statement, so nothing meaningful is delivered in the space used.

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 described, and annotations cover the safety profile. But for a six-parameter tool with three confusingly similar siblings, the definition omits the routing, default-range, and interval context an agent needs to invoke it correctly.

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% (all six parameters, including ticker, series_ticker, period_interval, and the timestamp bounds, are documented in the schema), so the baseline of 3 applies. The description adds no syntax, defaults, or interval-unit guidance beyond what the schema already provides.

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 market candlestick history' names the resource and adds the key detail that the output is candlestick (OHLC) data, which the bare name does not convey. However, it supplies no verb and does not distinguish this tool from very similarly named siblings such as kalshi_markets_history or kalshi_historical_market_history, leaving the agent to guess which history endpoint applies.

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 statement of when to use this tool, no prerequisites, and no mention of alternatives. With three near-identical history tools in the sibling list (kalshi_markets_history, kalshi_historical_market_history, kalshi_event_history), the absence of any routing guidance is a real gap.

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