subscribe_orderbook_updates

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

With no annotations, the description carries the burden of behavioral disclosure. It does convey that updates are delivered asynchronously whenever the orderbook changes and that levels are aggregated. However, it omits subscription lifecycle details such as whether updates continue until an explicit unsubscribe, how callback_type affects delivery, and whether an initial snapshot is sent.

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 sentences with no filler. The core action and resource are front-loaded, and the use case is stated efficiently. Every sentence adds value.

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?

The description is adequate for a basic invocation, especially with a fully documented schema. However, it leaves important operational context unstated: subscription lifecycle, how to stop updates, and the meaning/behavior of callback_type. No output schema exists to compensate for these 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 description coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond the schema: 'one or more tokens' restates token_ids, and it does not explain depth or callback_type semantics beyond what the schema already provides.

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 ('Subscribe') and resource ('real-time orderbook updates for one or more tokens'), and clarifies the output ('aggregated bid/ask levels'). It is clearly distinguishable from sibling tools like get_orderbook, which is a snapshot, and subscribe_market_prices, which targets price updates rather than orderbook levels.

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 gives a clear use case: monitoring liquidity and best bid/ask prices. It does not explicitly name alternatives or state when not to use it, but the real-time subscription framing provides enough context for an agent to choose it over a one-time get_orderbook call.

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