kalshi_series

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'credential-free' and 'public market-data' but does not describe important traits like pagination behavior, rate limits, or what constitutes a 'series row'. The return format is also unspecified. Essential behavioral details are missing.

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 that immediately states the purpose. It is concise with no filler. However, it could be slightly more informative while remaining concise. Front-loaded with the core purpose.

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 the tool has only two optional parameters and no output schema, the description is minimally adequate but insufficient. It does not describe the structure of the returned data or any constraints on the cursor. For a public data tool, users might need more context about what a 'series' is and how to use the cursor effectively.

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% for the two parameters (cursor and limit) with descriptions already provided. The tool description adds 'normalized rows' implying pagination but does not explain cursor usage or limit boundaries beyond what the schema states. Baseline 3 is appropriate as the description adds minimal additional semantic value.

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 returns normalized Kalshi series rows from public market-data JSON. The verb 'Returns' and specific resource 'normalized Kalshi series rows' make the purpose unambiguous and distinguish it from sibling tools like kalshi_event or kalshi_market.

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. There is no mention of scenarios, exclusions, or comparisons with sibling tools such as kalshi_series_detail or kalshi_markets. The description only states it is credential-free but does not help the agent decide if this is the right tool.

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