create_order

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

With no annotations provided, the description carries the behavioral disclosure burden and does so well. It explicitly lists four behavioral guarantees: session-bound account ID, positive volume validation, order type normalization, and full order state in the response. This goes beyond the bare 'create' semantics and gives agents meaningful expectations.

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 compact and front-loaded with the core purpose, followed by a tight bullet list of behavioral guarantees. Every sentence earns its place, with no fluff or redundant repetition of schema content.

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 is largely complete for a create operation: it names the resource, covers key validation and normalization behaviors, and notes the response shape. With full schema coverage and an output schema present, the agent has enough to invoke the tool correctly. Minor gaps remain around preconditions or when to prefer this over alternatives, but these are not critical.

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 100%, so the baseline is 3. The description adds value by explaining that account_id is always bound to the authenticated session, volume must be positive, and order_type is normalized to cTrader protocol values. These details enrich the otherwise minimal schema 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 opens with 'Create a new cTrader order,' which states a specific verb and resource. This clearly distinguishes it from sibling tools like cancel_order and amend_order, making the tool's role unmistakable.

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 no explicit guidance on when to use this tool versus cancel_order, amend_order, or list_orders. The verb 'Create' implies usage for new orders, but no alternatives, exclusions, or contextual conditions are stated.

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