kalshi_milestones

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, establishing a safe read operation. The description adds valuable context by specifying the return structure (cursor and milestone fields) and explicitly stating no auth is needed, which goes beyond the 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 concise and front-loaded with the core definition, then provides the return format and auth status in a structured manner. Every line contributes useful information, though the auth note is trivial but acceptable.

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 operation with optional parameters and no output schema, the description provides adequate context: what the tool returns, the response shape, and auth. It lacks explicit pagination guidance, but the schema covers cursor semantics. Overall, it is sufficiently complete for a simple listing tool.

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 input schema has 100% coverage with descriptions for all four parameters (limit, cursor, category, minimum_start_date). The tool description does not add any additional parameter-level detail, so it is at the baseline for full schema coverage.

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 defines what milestones are (dated catalysts linked to event tickers) and implies a retrieval operation. It distinguishes itself from sibling Kalshi tools by focusing on the milestone concept. However, it lacks an explicit verb like 'list' or 'get', which would make the purpose even more direct.

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?

There is no explicit guidance on when to use this tool versus other Kalshi tools (e.g., kalshi_events, kalshi_markets). The description only implies usage by defining the resource. No alternatives or exclusions are mentioned.

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