kalshi_get_event_metadata

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's mention of calling GET provides only marginal additional behavioral context. It does not disclose error behavior, permissions, or rate limits. 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?

Three sentences are compact, but the first sentence is slightly redundant: 'Get Event Metadata Endpoint for getting metadata...' repeats the tool name and purpose. Still, the description is focused and front-loaded with the key action.

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 simple metadata-fetching tool with one parameter and an annotation indicating read-only safe operation, the description provides the endpoint, return scope (metadata only), and differentiates it from full-event retrieval. It omits response structure, but that is not essential for this simple context.

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?

The schema fully covers the only parameter (event_ticker) with a description, and the description's reference to 'by its ticker' adds no distinct meaning beyond the schema. With high schema coverage, the baseline 3 is appropriate.

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 retrieves metadata for an event by its ticker, and explicitly says it returns only the metadata information, distinguishing it from sibling kalshi_get_event (full event data). The HTTP endpoint is also given, reinforcing the exact resource.

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 conveys the intended use case by noting it returns only metadata, which implies using this tool when metadata alone is needed versus the full event from kalshi_get_event. However, it does not explicitly name alternatives or state exclusions, so it stops short of full guidance.

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