kalshi_multivariate_events

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

No annotations are provided, so the description carries full burden. It mentions 'credential-free public market-data JSON' suggesting read-only public access, but does not explain pagination behavior, idempotency, rate limits, or what constitutes a 'multivariate event row'. This is insufficient for a tool with no annotation support.

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, but the first sentence ('Kalshi multivariate events.') is redundant with the tool name. The second sentence provides the core functionality. It could be more tightly structured by removing the tautology.

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 no output schema and no annotations, the description is too brief. It does not explain what 'multivariate events' are, how the cursor works, or what the response structure looks like. Among many Kalshi sibling tools, more context is needed to aid selection and correct usage.

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 the parameter schema is complete. The description adds no additional meaning to the 'cursor' or 'limit' parameters (e.g., format of cursor, default values). Baseline 3 is appropriate as schema covers technical details but description provides no extra context.

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 normalized Kalshi multivariate event rows from public market-data JSON. It distinguishes from siblings by noting that the regular events endpoint excludes these rows, making the tool's unique purpose explicit.

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 when to use this tool (when needing multivariate events not available via the regular endpoint) and notes it is credential-free. However, it does not explicitly state when not to use it or compare with other Kalshi tools beyond the regular events endpoint.

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