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, but the description adds nothing beyond that — no note on what the orderbook contains (bids/asks, depth), snapshot vs live behavior, or rate limits. A bare label on a data-fetch tool leaves real behavioral questions open.

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?

It is short, but that brevity is under-specification rather than economy — the phrase carries no information beyond the name. There is nothing to front-load because nothing was said.

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?

An output schema exists, so return values need not be described, but the description still omits any framing about the resource (a prediction-market orderbook) that would orient an agent. For a tool with a well-defined schema but a near-empty description, this is a clear completeness gap.

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% for the single required 'ticker' parameter, so the schema already documents it fully. Per the baseline rule for high coverage, a 3 is appropriate; the description adds no additional meaning (e.g., format of the ticker, where to obtain it).

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 'Kalshi market orderbook' is essentially a restatement of the tool name, with no verb and no statement of what is actually retrieved. An agent can infer it returns orderbook data for a Kalshi market, but it gets no help distinguishing this from siblings like kalshi_market, kalshi_market_history, or kalshi_markets_orderbooks.

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 guidance on when to use this tool versus alternatives such as kalshi_market_history or kalshi_markets_orderbooks (plural). The agent must infer usage entirely from the name.

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