createSpreadOrder

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 acknowledgement only, orders may be rejected asynchronously, and max 50 open orders per account. It also mentions authentication and symbol constraints. This is valuable behavioral context beyond a simple 'create order'.

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 sections for usage scenarios, important notes, and agent hint. Every sentence adds value, no redundancy. Concise yet informative.

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 no output schema, the description mentions async acknowledgement but not response format. It covers some parameters and behavioral constraints but omits details on error handling or success confirmation. Adequate but could be more complete.

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%, so the description must add meaning. It explains orderLinkId, timeInForce, and price (for limit orders), but does not describe side, orderType, or qty. Partial coverage adds some value but leaves gaps.

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 'Create a new spread trading order,' which is a specific verb and resource. It distinguishes from siblings like 'amendSpreadOrder' and 'cancelSpreadOrder' by focusing on creation. The usage scenarios further clarify the purpose.

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 includes explicit usage scenarios (opening new spread position, using orderLinkId, timeInForce) and important notes (async response, max 50 orders, price required for limit orders). It provides good context but does not explicitly compare to alternatives or state when not to use.

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