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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds only two extra facts: results are 'normalized' and no credentials are required. It does not mention pagination behavior or rate limits, so it adds modest value over the annotations.

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 sentence with no filler, and the resource and its source are front-loaded. Nothing in the text is redundant.

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 no explanation, and annotations cover the safety profile. The complete parameter documentation in the schema covers the interface; only routing (when to choose this list tool over history/orderbook siblings) is missing.

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 each of the six filters (limit, cursor, status, ticker, event_ticker, series_ticker) is documented in the schema itself. The description adds no filter syntax or format detail, so it does not exceed the schema baseline.

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+resource ('Returns normalized Kalshi market rows') and identifies the data source ('credential-free public market-data JSON'). It is distinguishable from the singular kalshi_market, but it never explicitly differentiates itself from close siblings like kalshi_markets_history or kalshi_historical_markets.

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?

No when-to-use guidance and no alternatives are named. The phrase 'credential-free public' implies it works without auth, but the description never states which of the many kalshi_* siblings to pick instead for history, orderbooks, or single-market lookups.

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