kalshi_get_exchange_status

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing the safety profile. The description adds the HTTP method and endpoint path, which is minor extra context, but it does not disclose any additional behavior such as response format, caching, or authentication requirements.

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 Exchange Status Endpoint for getting the exchange status' repeats the same idea. The endpoint information is valuable, but the phrasing could be tighter.

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 zero-parameter, read-only status endpoint, the description is adequate. However, since there is no output schema, it would benefit from a hint about what the response contains (e.g., 'returns a timestamp and status indicator'), but the current text is acceptable for a simple status check.

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 tool has zero parameters and the schema is empty, so the baseline is high. The description adds no parameter details because none exist; it correctly focuses on the action rather than parameters.

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 exchange status, with a specific verb ('Get') and resource ('Exchange Status'). It also identifies the exact API endpoint (GET /exchange/status), distinguishing it from sibling tools like kalshi_server_info or kalshi_get_exchange_schedule.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention related tools such as kalshi_server_info or kalshi_get_exchange_schedule, nor does it describe any prerequisites or typical use cases.

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