kalshi_get_event_forecast_percentiles

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context (mentions 'raw and formatted forecast numbers' and the GET method) but does not disclose potential rate limits, pagination, or response format details.

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 at two sentences and front-loads the purpose. The first sentence is slightly redundant ('Get... for getting...'), which prevents a perfect score, but it is efficient and free of unnecessary detail.

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 tool with complete schema coverage and safety annotations, the description is adequate. It clearly states the endpoint and the type of data returned, though it does not detail the response structure, which is acceptable given no output schema and the straightforward nature of the 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?

All six parameters have descriptions in the schema (100% coverage), so the schema already documents their meaning. The description adds no additional parameter-level semantics beyond what is already in 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 names the specific resource (Event Forecast Percentile History) and action (Get), distinguishing it from sibling tools like kalshi_get_event by its focus on historical forecast values at percentiles. The inclusion of the exact API endpoint further reinforces the purpose.

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?

Usage context is implied by the resource type and endpoint, but there is no explicit guidance on when to choose this tool over alternatives or any exclusions. It does not reference sibling tools or state conditions for use.

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