kalshi_event

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

With no annotations, the description provides minimal behavioral context: it is a read operation that returns event data optionally with markets. It does not disclose any potential side effects, authorization needs, or data freshness. The return structure is specified, which helps.

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, consisting of two short sentences. The first sentence states the core functionality, and the second provides the return object structure. No filler or redundant information.

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?

The description covers the basic purpose and return format but lacks completeness given no annotations or output schema. It does not mention error handling, behavior when ticker is invalid, or confirm it is a read-only operation. For a simple retrieval tool, it is minimally adequate.

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%, so the description must compensate. It adds meaning for 'with_nested_markets' by stating it controls embedding of markets, but provides no detail on the 'eventTicker' parameter format or possible values beyond being a ticker identifier.

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 retrieves a single event by ticker, optionally including nested markets. It distinguishes itself from sibling tools like kalshi_events (plural) and kalshi_market by specifying singleton retrieval.

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 usage for fetching a single event by ticker but does not explicitly state when to prefer this over kalshi_events or other event-related tools. No when-not-to-use or alternative guidance is provided.

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