kalshi_batch_get_market_candlesticks

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

Beyond the readOnlyHint annotation, the description discloses significant behavioral traits: response limits, grouping behavior, and the optional synthetic candlestick logic including its algorithmic details. This goes well beyond the annotation's simple read-only declaration.

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 concise, with three bullet-style sentences plus an endpoint reference. It front-loads the purpose, lists key constraints in a scannable format, and contains no filler or redundancy.

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?

Given a read-only batch tool with no output schema, the description covers essential aspects: limits, grouping, and the optional synthetic behavior. It does not describe the candlestick data structure, but that is likely predictable from the domain, and the input schema is thoroughly documented. This is sufficiently complete but not exhaustive.

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 100%, so baseline is 3. The description adds value by explicitly highlighting the include_latest_before_start parameter and explaining its price-continuity purpose, which supplements the schema's own detailed description. This earns a 4.

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 the tool retrieves candlestick data for multiple markets via a batch endpoint, using specific verbs like 'Batch Get' and 'retrieving'. It distinguishes itself from sibling tools by emphasizing 'multiple markets' and the 100-ticker limit.

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?

The description implies usage for fetching data across multiple markets, with explicit limits (up to 100 tickers, 10,000 candlesticks) and grouping by market_id. However, it does not explicitly name alternatives or state when not to use it, though batch vs. single-market context is clear from sibling names.

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