List Kalshi events

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

While annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false) already declare the tool's safety profile, the description adds no additional behavioral context such as pagination behavior, rate limits, or data freshness. It merely restates the tool's purpose without elaboration.

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 extremely concise with a single sentence, containing no fluff. However, it lacks front-loading of key details like the optional nature of nested markets, and could benefit from a slightly more structured format (e.g., listing key features).

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 4 parameters, no output schema, and is a list operation, the description is incomplete. It fails to mention pagination (cursor/limit), status filtering, or what the return format looks like. The tool's behavior in terms of sorting or default limits is also absent.

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?

With 0% schema description coverage, the description only adds meaning for one parameter: 'Optionally include nested markets' corresponds to with_nested_markets. The other parameters (limit, cursor, status) are completely unexplained, leaving the agent to infer their purpose from names alone.

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 lists events (groups of related markets) with an option to include nested markets, distinguishing it from sibling tools like kalshi_list_markets (individual markets) and kalshi_get_event (single event). The verb 'list' and resource 'events' are specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives (e.g., kalshi_list_markets, kalshi_get_event). There is no mention of prerequisites, common use cases, or scenarios where other tools are more appropriate.

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