okx_cancel_order

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

The description labels the tool as a write operation but provides no additional behavioral details such as authentication requirements, side effects, or reversibility. With no annotations, the description carries the full burden and falls short.

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 unclear and cryptic. It wastes the opportunity to convey purpose and guidance. Conciseness should not sacrifice 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 complexity of the trading system and the lack of output schema, the description is inadequate. It does not specify return values, error handling, or the effect of cancellation, leaving the agent underinformed.

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?

Both parameters are described in the input schema with Chinese labels, but the description adds no further meaning. Since schema coverage is 100%, the baseline score is 3, and the description does not improve on it.

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 only provides a category label and a reference to agent_catalog, but does not explicitly state that the tool cancels an order. The name implies the purpose, but the description fails to confirm it clearly.

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 is given on when to use this tool versus alternatives like okx_cancel_all or okx_batch_cancel_orders. The description does not mention prerequisites or context.

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