Kalshi public trade history

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description adds that it returns 'executed prints' and can cover the whole exchange or one market. No contradiction with annotations, but lacks details like rate limits or pagination behavior beyond cursor usage.

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 two sentences plus a code example—no redundant information. Purpose is front-loaded, and parameters are explained concisely. Every sentence adds value.

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?

With no output schema, the description does not specify return fields (e.g., price, size, time). It mentions 'executed prints' but lacks detail for an agent to fully anticipate the response. For a paginated list tool, more info on result structure would improve completeness.

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 coverage is 67% (ticker and cursor have descriptions, limit lacks description but has defaults). The description mentions ticker and cursor but not limit semantics. The example provides context for typical usage but does not deeply elaborate on parameters. Baseline 3 is appropriate given coverage.

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 clearly states it returns 'Public trade history (executed prints)' and distinguishes between exchange-wide or per-market via filter. It differentiates from siblings like kalshi_candlesticks (aggregated price data) and kalshi_orderbook (order book).

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?

It explains filtering by ticker and pagination with cursor, implying use for raw trade data. However, it does not explicitly contrast with alternative tools like kalshi_candlesticks or kalshi_orderbook, so usage guidance is clear but not exhaustive.

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