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 no behavioral context beyond that: no defaults for period_interval, no upstream-support caveats, no rate limits or pagination behavior.

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 short but under-specified rather than concise: a four-word fragment for a six-parameter tool. No front-loaded action verb, no scoping constraint, nothing that would let an agent act without opening the schema.

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, but for a six-parameter historical-data tool with no usage guidance and no behavioral notes, the definition is too thin to be complete.

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 all six parameters (timestamps, tickers, interval, include_latest_before_start) are documented in the schema. The description contributes nothing beyond that, which is the expected baseline of 3 when the schema does the heavy lifting.

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 identifies a resource (Kalshi event candlestick history) and the data type (candlesticks), which is marginally more than the name restates. However, it is a noun fragment with no verb and does not distinguish itself from close siblings such as kalshi_market_history or kalshi_markets_history, leaving the agent to infer event-level vs market-level scoping.

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 when-not-to-use, and no mention of any alternative sibling. The agent gets no signal about when this tool is preferred over kalshi_market_history or kalshi_events.

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