kalshi_price_history

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

With no annotations, the description must disclose behavioral traits. It mentions 'from accumulated snapshots' as a data source, but fails to convey return format, time range, update frequency, or any limitations. There is no indication of pagination, sorting, or error conditions.

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?

The description is a single sentence with no filler words. It is front-loaded with the core concept and remains appropriately brief. Every word contributes to the basic meaning, showing excellent conciseness.

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?

The tool is simple (one parameter, no output schema), but the description still misses critical context. It does not mention what the returned history contains, how far back it goes, or any usage context. Given no annotations and no output schema, the description leaves the agent uncertain about the tool's full behavior.

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?

The schema has zero description coverage for the 'ticker' parameter, and the description only adds 'one market' to suggest ticker identifies the market. It does not explain ticker format, how to find valid tickers, or relationship to other kalshi tools. The description partially compensates but remains insufficient for a 1-param tool with no schema documentation.

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 description states it provides 'recorded price history for one market,' which is specific about the resource (price history) and scope (one market). It distinguishes from sibling tools like kalshi_snapshot_now (current snapshots) and kalshi_market_detail (market details). However, it lacks an explicit verb like 'get' or 'retrieve,' making the action implied rather than directly stated.

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?

No guidance is given on when to use this tool versus alternatives. The description only implies it is for historical price data, but does not mention when to prefer it over kalshi_snapshot_now or other data sources. No exclusions or preconditions are provided.

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