okx_place_order

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

Without annotations, the description carries the full burden. It discloses key behaviors: it places market orders (not limit), SWAP orders set leverage and optional SL/TP, SPOT orders are simple, and the confirm parameter allows preview before execution. This is substantial but does not cover execution details or post-order 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?

Two sentences, front-loaded with the purpose, no wasted words. It efficiently conveys the tool's core function and per-mode behavior.

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?

The description covers the essential modes and confirm behavior. Given no output schema, it might be expected to mention return values, but the essential functionality is clear. It is slightly abbreviated but complete enough for a place-order tool.

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 88%, so baseline is 3, but the description adds meaningful context by tying leverage, SL/TP to SWAP and SPOT simplicity, and explaining confirm's preview behavior. This goes beyond the schema's individual parameter descriptions.

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 clearly states 'Place a market order on OKX', using a specific verb and resource. It further distinguishes behavior between SWAP and SPOT, making it distinct from sibling tools like okx_get_ticker or okx_get_balance.

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?

It gives clear context on when to use the tool (to place market orders) and differentiates between instrument types (SWAP with leverage/SL/TP, SPOT simple buy/sell). However, it does not explicitly mention alternatives or when not to use it, so it stops short of a 5.

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