createOrder

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

With no annotations, the description carries full burden. It discloses that the response is an acknowledgment and advises using WebSocket for confirmation. It covers support for various order types and categories. However, it omits behavioral details like authentication requirements, rate limits, or potential side effects on positions.

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 well-structured with bullet points and breaks down by category. It front-loads the core purpose. Although it is moderately long due to the complexity of the tool, it remains efficient and avoids redundancy.

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 (34 parameters, no output schema, no parameter descriptions in schema), the description addresses the main use cases and key parameters. However, it does not fully cover all parameter interactions or provide examples for all order types (e.g., conditional orders, TP/SL setups), leaving some gaps for an AI agent.

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 description coverage is 0%. The description adds meaning for key parameters like orderFilter, positionIdx, orderLinkId, and orderIv, and explains category usage for TradFi tokens. However, many parameters (e.g., timeInForce, triggerPrice, takeProfit) remain unexplained, so the description only partially compensates for missing schema documentation.

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 new order on the Bybit exchange' and elaborates on supported categories (spot, linear/inverse, options) and specific token examples. It effectively distinguishes from sibling tools like amendOrder, cancelOrder, etc., by focusing on order creation.

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 provides clear guidance on when to use this tool ('to place a new buy or sell order for spot, linear, inverse, or option products') and includes TradFi examples. It lacks explicit exclusion criteria or alternative tools for specific scenarios, but the context is sufficient for most cases.

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