kalshi_exchange_schedule

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

With no annotations provided, the description carries full burden but only states the content of the return object. It does not disclose behavioral traits such as read-only nature, permission requirements, rate limits, or whether the schedule is static or dynamic.

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 – two sentences that front-load the main purpose and provide the return structure. There is no superfluous 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?

Given no parameters and no output schema, the description is minimal but adequate for a simple schedule retrieval tool. However, it could benefit from providing example values or clarifying the format of fields like 'standard_hours' and 'maintenance_windows'.

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 input schema is fully covered by an empty object. Per guidelines, baseline score of 4 is appropriate since no parameter documentation is needed beyond the schema.

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 returns 'Standard trading hours + maintenance windows', specifying the exact resource and output. It distinguishes itself from sibling tools like kalshi_event or kalshi_market by being the only schedule-related tool for Kalshi.

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 explicit guidance on when to use this tool versus alternatives. Although it's implied to retrieve schedule information, there is no mention of prerequisites, scenarios to avoid, or comparisons to other Kalshi tools.

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