okx_mass_cancel

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention that this is a write operation, what it cancels (all orders? specific types?), any side effects, or required permissions. The description is insufficient for an agent to understand the tool's 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 extremely short but fails to convey essential information. It is under-specified rather than concise. Every sentence should earn its place, but here the only substantive instruction ('请先调用 agent_catalog') does not explain the tool itself.

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 2 parameters, no output schema, no annotations, and a nearly useless description, the tool is incomplete. The agent cannot determine what the tool returns, what constitutes a successful call, or how to interpret results. This is far from adequate.

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 coverage is 100% (both parameters have descriptions in the schema), so the schema provides basic parameter meaning. However, the description adds no extra context about how parameters affect the mass cancellation. The baseline is 3 for high coverage, but the description contributes nothing, so a 2 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 fails to state what the tool does. It contains tags like '[L:WRITE]' and a Chinese instruction to call agent_catalog first, but no verb or resource indicating the tool's action. The tool name 'okx_mass_cancel' suggests mass cancellation of orders, but the description does not confirm this.

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 versus alternatives. The only instruction is to call agent_catalog first, which is a prerequisite but does not help the agent decide when to invoke this tool over other order-canceling tools.

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