kalshi_series_list

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

Description implies a read-only listing operation but does not explicitly state its non-destructive nature or disclose any authentication requirements, rate limits, or side effects. No annotations provided, so the description carries the full burden.

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 sentences plus an example; front-loaded with the core purpose. The list of categories is slightly verbose but aids understanding. No wasted words.

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?

Provides the return format but lacks information on pagination, limits, error handling, or the effect of optional parameters. Adequate for a simple listing tool but could be more complete.

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 0% and the description only mentions the 'category' property indirectly by listing allowed values. Does not explain the 'include_product_metadata' parameter or provide any constraints/format details. The return structure is shown but not parameter meanings.

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 'All series in a category' and lists example categories (Sports, Politics, etc.). Distinguished from sibling kalshi_series which likely returns a single series.

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?

Explicitly requires a 'category' parameter and provides context for when to use it (top of id chain). Does not specify when not to use or alternatives, but the usage is clear from context.

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