create_draft_order

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

No annotations are provided, so the description must bear full weight. It fails to disclose what happens after creation (e.g., if the draft order is immediately open, whether it returns an ID, or if further steps like completing are required). This is a significant gap for a creation tool.

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 with front-loaded purpose. Concise, but could be slightly more structured. Still, it is efficient and wastes no words.

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 8 parameters, nested objects, and no output schema, the description should mention the return value and lifecycle context. It lacks explanation of what is returned or how this fits with sibling tools like 'complete_draft_order'. It is minimally adequate but not comprehensive.

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?

Although the schema covers all parameters 100%, the description inaccurately mentions 'billing addresses' while the schema only includes 'shipping_address'. This mismatch can mislead the agent. The description adds little beyond the schema for other parameters.

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 starts with 'Create a new draft order', clearly stating the verb and resource. It mentions key components like line items and optional customer, which distinguishes it from sibling tools like 'get_draft_order' or 'complete_draft_order'.

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 does not provide explicit guidance on when to use this tool versus alternatives such as 'complete_draft_order' or 'update_draft_order'. It only states what to provide, not the context or lifecycle.

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