kalshi_get_series_fee_changes

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds minimal behavioral detail beyond the endpoint path. It does not disclose the response format, pagination, or the meaning of historical data, so the agent still lacks key behavioral context.

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 one concise sentence that directly states the purpose and endpoint. While somewhat terse, it is free of redundant or irrelevant content.

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 API tool with optional parameters, the description should clarify what fee changes are, how the parameters affect the results, and how it differs from related tools. None of this is provided, leaving significant gaps for an agent to invoke the tool correctly.

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 has two parameters with no descriptions, and the description does not mention them at all. With 0% schema description coverage, the description carries the full burden and fails to explain series_ticker or show_historical.

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 identifies the resource 'Series Fee Changes' with the verb 'Get', and the HTTP endpoint reinforces the action. It distinguishes from sibling tool kalshi_get_event_fee_changes by the resource type (series vs event), though it does not explain what fee changes are.

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 like kalshi_get_event_fee_changes. There is no mention of prerequisites, such as needing a series_ticker, or when to set show_historical.

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