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

With no annotations provided, the description carries the full transparency burden. It conveys that the data is live and includes bid/ask depth, and it names both supported venues. It does not disclose response behavior, staleness, or any side-effect profile, though the output schema covers return values.

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?

The description is one direct, front-loaded sentence with no filler. The examples are relevant and compact, and the sentence earns every word.

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 simple two-parameter orderbook tool, the description covers the core argument and use case, and the output schema supplies return structure. Still, the undocumented optional platform parameter and lack of explicit alternative guidance leave minor but real gaps.

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 coverage is 0%, so the description must compensate. It explains ticker_or_token well with concrete Kalshi and Polymarket examples, but the optional 'platform' parameter is never described. Its meaning, allowed values, and relationship to ticker_or_token remain undocumented.

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 uses a specific action ('fetch'), a precise object ('live bids and asks orderbook depth'), and concrete examples for both supported inputs. This makes it clearly distinct from sibling tools like price_history, recent_trades, or live_data.

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 description clearly states the intended scenario: obtain current bid/ask depth for a Kalshi ticker or Polymarket YES-token ID. However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of full routing guidance.

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