okx_ws_subscribe_private

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

No annotations are present, so the description must carry the full burden. It only hints at read-only behavior with '[L:READ]' but fails to disclose important behavioral traits such as the need for prior authentication, the fact that it establishes a long-lived WebSocket connection, or what happens upon subscription (e.g., data streaming).

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 very short, which is concise, but it lacks essential information. It front-loads a prerequisite instruction, but the overall structure is too sparse to be effective. While brevity is valued, it sacrifices clarity and completeness.

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 tool's complexity (WebSocket subscription), the absence of annotations and output schema, and the cryptic description, the context is severely incomplete. The description does not explain the return values, side effects, or the lifecycle of the subscription, making it difficult for an 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 description coverage is 100%, so the baseline is 3. The tool description adds no additional meaning to the parameters beyond what the schema already provides. It does not explain the channel values or the instId field, which are fully documented in the schema.

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 is vague and does not clearly state the purpose of the tool. It only contains cryptic tags like '[L:READ]' and 'CAT:[行情-WS]' without explaining that the tool is for subscribing to private WebSocket channels. The instruction '请先调用 agent_catalog' is a prerequisite, not a purpose statement.

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?

Minimal usage guidance is provided. The description instructs to call 'agent_catalog' first, but it does not specify when to use this tool over alternatives or provide any context about the appropriate scenarios for private subscription. No exclusions or comparisons with siblings are given.

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