okx_ws_events

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, return format, or authentication needs. The '[L:READ]' hint is insufficient to convey behavior.

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 but fragmented with brackets and Chinese. It is not well-structured for an English-speaking AI agent, and the cryptic format reduces 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?

Given the tool's likely role in listing WebSocket events, the description is severely incomplete. No output schema is present, and the description does not explain what the tool returns or how the parameters are used beyond basic schema definitions.

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?

All three parameters (limit, filter, subscriptionId) have descriptions in the input schema, covering 100% of parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 cryptic: '[L:READ] CAT:[行情-WS] | → 请先调用 agent_catalog'. It vaguely suggests a read operation for WebSocket market data but does not provide a clear verb+resource. The tool's purpose is unclear without external context.

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?

The description includes a prerequisite ('请先调用 agent_catalog'), but no guidance on when to use this tool versus alternatives like okx_ws_subscribe or okx_ws_status. The context is minimal and not actionable.

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