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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and scope profile is covered. The description adds that the data are 'normalized' and sourced from 'public orderbook JSON', which is genuinely useful context about the shape and origin of the data. It does not discuss depth, pagination, or freshness of the book, so it is a modest addition rather than rich behavioral 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?

Two short sentences, with the core return description front-loaded and the cross-reference second. Nothing is redundant or padded.

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-value documentation is not required, and annotations cover the read-only/open-world profile. What remains is a clear statement of what is returned plus a pointer to the detail tool. Slightly incomplete in that it never mentions the batch orderbook sibling or any depth/limit characteristic of the book.

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 parameter already documents itself as 'Kalshi market ticker.' The description repeats the same 'Kalshi market ticker' concept without adding format, example, or resolution guidance. Baseline 3 is appropriate when the schema carries the parameter semantics alone.

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 states a specific verb and resource: it returns 'normalized yes/no bid levels' for a Kalshi market ticker's orderbook. This is a clear operation an agent can match against siblings like kalshi_market and kalshi_market_history. It does not, however, explicitly distinguish itself from the batch sibling 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?

The sentence 'Use kalshi_market to retrieve kalshi market detail' points at a related tool, which implies this tool should be reached after obtaining a ticker. But it gives no explicit when-to-use vs when-not guidance and does not mention the plural batch alternative kalshi_markets_orderbooks, leaving the choice between the two to inference.

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