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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: it is 'credential-free', telling the agent no API key is required, and identifies the source as public market-data JSON. It does not cover rate limits or freshness, but it earns credit for the auth-need disclosure.

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?

A single front-loaded sentence with no filler, and the resource list appears before the data-source qualifier. Slightly redundant with the repeated 'Kalshi' and the triple-item noun stack, but it is efficient.

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 single-parameter read tool with an output schema (so return values need no explanation) and annotations covering safety, the description is largely sufficient. The one real gap is routing guidance against the many kalshi_* siblings, which keeps it from a 5.

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% and the single event_ticker parameter is fully documented with an example (KXELONMARS-99). The description adds no format, naming, or lookup guidance beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Returns') and enumerates the resource content precisely: event media, market-detail, and settlement-source metadata. It is clear what the tool produces, but it never distinguishes itself from the close sibling kalshi_event or kalshi_market, so an agent cannot tell from the text alone which one to reach for.

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 when-to-use statement, no prerequisites, and no mention of the alternatives (kalshi_event, kalshi_event_history, kalshi_market). The only contextual hint is 'credential-free public market-data JSON', which describes the data source rather than when to select this tool.

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