kalshi_get_milestones

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds only 'Calls GET /milestones,' which is marginal; it does not disclose pagination behavior, rate limits, or result shape, and there is no output schema to compensate.

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 structurally garbled—purpose, a parameter description, a format note, and an endpoint reference are run together without clear separation. 'Minimum start date to filter milestones.' reads as an orphaned sentence.

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 9-parameter tool with no output schema and a near-identical singular sibling (kalshi_get_milestone), the description fails to explain what a milestone is, what the response contains, or how this tool relates to its sibling. The schema covers parameters but not the broader context an agent needs.

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 description coverage is 100%, so parameters are already well documented. The description's only parameter-related content ('Minimum start date... Format: RFC3339 timestamp') merely duplicates the minimum_start_date schema description and adds no new semantic value.

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 opens with 'Get Milestones,' a clear verb+resource pair that identifies the list operation. However, it does not differentiate from the sibling tool kalshi_get_milestone, and the following fragments about minimum_start_date add confusion rather than scope.

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 given on when to use this tool versus kalshi_get_milestone or other list tools. It doesn't mention polling use cases (despite min_updated_ts) or pagination strategy, leaving the agent to infer usage from the schema alone.

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