okx_place_algo_order

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

No annotations are provided, and the description lacks any behavioral details such as authentication requirements, rate limits, or error handling. The '[L:WRITE]' hint is minimal and insufficient.

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 favors conciseness, but it is not clearly structured for an AI agent, using brackets and Chinese labels that may be opaque. It sacrifices clarity for brevity.

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?

Placing an algorithmic order is a complex operation requiring many parameters (e.g., instrument, size, algo type). The description provides no guidance on parameters, return values, or prerequisites beyond calling agent_catalog. This is severely incomplete.

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?

The only parameter 'params' is an object with a vague description referencing OKX docs. This adds little meaning beyond the schema, which is also generic (additionalProperties allowed). The agent gains no insight into required fields or structure.

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 labels like '[L:WRITE]' and 'CAT:[交易-委托]' instead of a clear statement of what the tool does. While the name suggests placing an algorithmic order, the description does not explicitly state that purpose, leading to ambiguity.

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 only provides a prerequisite ('请先调用 agent_catalog') but offers no guidance on when to use this tool versus alternatives like 'okx_place_order' or other algo order tools, nor does it explain exclusions or context.

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