kalshi_get_multivariate_events

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context about events being dynamically created and calls the GET endpoint, but does not disclose pagination behavior, rate limits, or other operational details. No contradiction with annotations.

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 short but contains redundancy: 'Get Multivariate Events' and 'Retrieve multivariate (combo) events' say the same thing. The overall length is acceptable, but the wasted repetition prevents a higher score.

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?

For a read-only list endpoint with a comprehensive schema and annotations, the description adequately covers the core purpose and primary filters. However, it lacks explicit differentiation from sibling event tools and does not guide on pagination or nested market options, though these are in the schema.

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 description coverage is 100%, so the baseline is 3. The description mentions filtering by series and collection ticker, which maps to two parameters, but adds no additional meaning beyond the schema for limit, cursor, or with_nested_markets.

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 identifies the resource as multivariate (combo) events with the verb 'Get'/'Retrieve'. It distinguishes from sibling event tools by emphasizing the dynamic creation from collections and filtering by series/collection ticker.

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?

It provides clear context for when to use this tool—when multivariate/combo events are needed—but lacks explicit exclusions or alternatives. The description implies usage rather than detailing when not to use it versus kalshi_get_events or other siblings.

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