subscribeKline

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

Annotations already mark the tool as read-only and open-world, so no contradiction exists. However, the description adds almost no behavioral context beyond 'push': it does not disclose whether messages arrive continuously, how timeoutMs or messageCount affect the stream, or whether an explicit stopSubscription is required.

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 extremely short and free of fluff, which is good for conciseness. However, it is under-specified: the single phrase carries only the core action and resource, without the structure or context needed to be genuinely useful.

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 five parameters and no output schema, this description is far too thin. It does not explain how subscription messages are delivered, how long the subscription lasts, what the message payload contains, or how this relates to startSubscription/stopSubscription siblings.

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 description does not compensate. The five parameters, including required symbol and interval, are left entirely unexplained in the description; the schema only provides types, enums, and defaults, not their semantics.

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 clear verb and resource: '订阅 K 线推送' (subscribe to K-line push). This distinguishes it from sibling tools like getMarketKline or subscribeTickers, but it adds little beyond what the tool name already implies and does not specify what kind of K-line data is pushed.

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?

There is no guidance on when to use this tool versus alternative subscribe tools such as subscribeTickers or subscribeOrderbook, nor versus fetching K-lines via getMarketKline. The description gives no context about subscription lifecycle, prerequisites, or stopping the subscription.

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