Compare markets in an event

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 real value by revealing the return shape (only open markets, ranked by YES price, with YES bid/ask totals), but it omits behavior for empty events, default sort direction, and any result limits.

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; the most useful information (open markets, ranking key, bid/ask totals) comes first. Room remains for one more short clause on ordering or the ticker format at no cost to readability.

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?

With no output schema and thin annotations, the description partially compensates by sketching the return contents. It is still incomplete on the ambiguities an agent would hit when calling it: sort direction of 'ranked by YES price', empty-event behavior, and result count limits.

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 0% and the single event_ticker parameter has no schema-level description. The description only implies the parameter's role ('in one Kalshi event') and gives no format or example for an event ticker, leaving the required argument underspecified beyond its type.

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 specifies the resource and scope concretely: 'All open markets in one Kalshi event ranked by YES price, with YES bid and ask totals.' That tells an agent this is a per-event market listing rather than a single-market lookup. It does not explicitly contrast itself with get_market or search_markets, so sibling differentiation is left partly to the title.

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 statement of when to use this versus get_market, search_markets, or get_market_evidence, and no exclusions or prerequisites (e.g., 'requires a valid event ticker'). An agent has to infer usage purely from the resource wording.

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