create_order

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

No behavioral traits disclosed. Given no annotations, the description should mention whether the order is atomic, results, or any side effects. It does not even confirm order creation happens.

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?

Extremely concise but uninformative. Single sentence that barely expands on the tool name. The description should be front-loaded with key behavior but provides no structure.

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?

With 13 parameters, no output schema, and no annotations, the description fails to provide necessary context about parameter relationships, constraints (e.g., order_price required for LIMIT), or typical usage. Completely inadequate.

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 covers all parameters with descriptions (100% coverage). The tool description adds no new parameter meaning beyond the schema, which already provides basic info. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'Create a new regular order'. It implicitly distinguishes from 'batch_create_orders' and 'create_algo_order', but does not explicitly contrast them.

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 on when to use this tool versus alternatives like 'batch_create_orders' or 'create_algo_order'. Missing prerequisites or context for order type selection.

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