okx_cancel_algo_order

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

No annotations are provided. The description only includes a generic write tag '[L:WRITE]' and a category tag, missing important behavioral details such as idempotency, side effects, required permissions, or error conditions. The description does not add value beyond the tags.

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 not effectively structured. It uses cryptic abbreviations and non-English tags that hinder clarity. It is not front-loaded with the tool's purpose and fails to earn its place.

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 (two parameters, no output schema), the description is critically incomplete. It lacks information about return values, cancellation constraints, or any context that would help an agent use it 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?

Input schema coverage is 100% with both 'algoId' and 'instId' having descriptions (but these are in Chinese and not in the description). The description adds no additional meaning to the parameters, so baseline score of 3 applies.

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 uses cryptic tags like '[L:WRITE]' and 'CAT:[交易-委托]', which do not clearly state the tool's purpose. The tool name 'okx_cancel_algo_order' combined with input schema (algoId, instId) hints at cancellation, but the description fails to explicitly state that the tool cancels an algorithm order.

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 alternatives. The description does not mention conditions, prerequisites, or context for use. The phrase '→ 请先调用 agent_catalog' (Please call agent_catalog first) is a vague instruction without explanation.

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