subscribeKline

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

No annotations are provided, and the description fails to disclose behavioral traits such as whether the subscription is continuous, how to manage the subscription lifecycle, data delivery frequency, or limitations. The agent has no information about side effects or requirements.

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 (one sentence), which is concise but at the expense of crucial information. It does not earn its place by providing meaningful content beyond the tool's name.

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?

Given the complexity of 5 parameters, no annotations, no output schema, and many sibling subscription tools, the description is severely incomplete. It lacks essential details about subscription behavior, parameter usage, and how to stop the subscription, making it inadequate for an AI agent to invoke 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?

With 0% schema description coverage and no parameter explanations in the description, the agent has no understanding of the meaning of 'interval', 'symbol', 'category', 'messageCount', or 'timeoutMs'. The description adds no value beyond the schema's structural definition.

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 '订阅 K 线推送' clearly indicates that the tool subscribes to K-line (candlestick) push data. This distinguishes it from sibling subscription tools like subscribeOrderbook or subscribeTickers, but it does not specify the exact resource (e.g., market K-line vs. index price K-line) or provide additional context beyond the 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 guidance is provided on when to use this tool versus alternatives such as getMarketKline for polling or other subscription tools. The description lacks explicit context for when a subscription is appropriate or how it differs from one-time data retrieval.

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