bookticker_subscribe

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

With no annotations, description carries full burden. It does not mention that subscription may require an active websocket connection, rate limits, or the nature of the stream updates. Very sparse behavioral disclosure.

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?

Extremely concise: two sentences and an arg list. No unnecessary words, though the structure could be improved with sections for clarity.

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?

Lacks context about side effects (e.g., subscription management), prerequisites (like websocket connection), and output details despite having an output schema. Incomplete for a subscription tool.

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?

The parameter 'market' is described in both the tool description and input schema with similar wording ('Market pair (e.g., 'BTC_USDT')'). No additional semantics beyond what schema provides. Schema coverage 0% per context, but actual schema has description, so baseline 3.

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?

Description clearly states the action 'Subscribe', the resource 'BookTicker stream', and the required market parameter, distinguishing it from sibling 'bookticker_unsubscribe'.

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 on when to use this tool vs alternatives like 'connect_websocket', 'get_ticker', or 'get_orderbook'. Implies usage only through name and description.

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