subscribeOrderbook

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

The description only says 'subscribe', which implies a subscription that sends updates, but it lacks details on duration, unsubscription behavior, rate limits, or whether it's a one-time snapshot. Annotations are absent, so the description carries full burden but fails to disclose critical behavioral traits.

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 a single sentence, very concise, but it sacrifices necessary detail. Being concise is positive, but the brevity leads to under-specification, missing key information.

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?

With 5 parameters, no output schema, and no annotations, the description is too brief to be complete. It does not explain subscription behavior, parameter roles, or usage context, making it inadequate for an AI agent to use correctly.

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%, and the description adds no information about any of the 5 parameters. The agent must rely solely on the schema, which may not clarify the meaning of 'messageCount', 'timeoutMs', or how 'depth' values correspond to levels. Description offers zero parameter guidance.

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 states it subscribes to order book depth snapshots, specifying the mode. It distinguishes from siblings by mentioning 'subscribe-snapshot mode', but could be clearer on how it differs from other orderbook subscriptions like 'subscribeRpiOrderbook'.

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 guidance is provided on when to use this tool versus alternatives (e.g., getOrderbook, subscribeSpreadOrderbook). There is no mention of when-not-to-use or context for selecting this subscription type.

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