kalshi_market_history

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

No annotations provided. Description only mentions credential-free access and normalized output. Does not disclose rate limits, data freshness, error handling, or pagination behavior. For a data retrieval tool with no annotations, more transparency is needed.

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 efficient sentences with no filler. The first sentence restates the name, but the second provides critical information about normalization and credential-free access.

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?

No output schema; description partially compensates by mentioning 'normalized Kalshi candlesticks' but lacks field details. Parameters are documented, but return structure is too vague for a data retrieval tool.

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?

All 6 parameters have schema descriptions, so baseline is 3. Description adds no extra meaning beyond what 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?

Clearly states it returns candlesticks for one Kalshi market, distinguishing it from siblings like kalshi_market or kalshi_event_history. The verb 'returns' and object 'normalized Kalshi candlesticks' are specific.

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 explicit when to use or when not to use compared to other history tools. Mentions 'credential-free' but lacks guidance on selecting this over siblings like kalshi_historical_market_history.

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