subscribeSpreadOrderbook

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

The annotations already declare readOnlyHint and openWorldHint, and the description adds no behavioral context beyond the word 'subscribe'. It does not disclose whether the call returns after timeoutMs or messageCount, whether the subscription is one-shot or continuous, or what the orderbook stream actually contains.

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 phrase is short and front-loaded with the key idea, with no filler words. But it is too terse to be a genuinely helpful definition, and there is no structured explanation of behavior or parameters.

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 subscription tool with no output schema and no parameter descriptions, the definition is incomplete. It omits return-value semantics, subscription duration behavior, and how timeoutMs and messageCount control the call, leaving an agent to guess.

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 0% and the tool description does not mention timeoutMs or messageCount at all. The parameter names and defaults communicate little about their intended meaning, so the description must compensate and fails to do so.

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 clearly names the action (订阅/subscribe) and the resource (Spread 订单薄/orderbook), so an agent can tell it apart from unrelated tools. However, it does not explicitly contrast with nearby siblings like getSpreadOrderbook or subscribeSpreadOrder, and it reads mostly as a translation of the tool name.

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 usage guidance is provided. It does not say when to prefer this over getSpreadOrderbook (snapshot vs stream) or subscribeSpreadOrder (order events vs orderbook), nor does it describe any prerequisites or context for when the subscription is appropriate.

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