create_order

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

Annotations only include openWorldHint: false, providing no safety or side-effect information. The description says 'Create a new order' but does not disclose whether totals are auto-calculated, whether payment is required, if customer creation is needed, or what happens on failure. For a mutating e-commerce tool, this lacks behavioral transparency.

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 two sentences and 21 words, front-loaded with the core purpose. Every phrase adds value, and it avoids unnecessary verbiage.

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?

For a 9-parameter tool with nested objects and no output schema, the description is minimal. The schema covers parameter definitions well, but the description does not mention return value, default status behavior, or how optional billing/shipping/customer fields interact with the order creation. It is adequate but leaves gaps.

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 coverage is 100% with all parameters described, so baseline is 3. The description adds genuine semantic value with 'Use variation_id for variable product variants,' clarifying when to use that parameter beyond its schema description. The rest of the parameter guidance is redundant with the schema.

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 order,' which is a specific verb and resource that clearly distinguishes from sibling tools like update_order, delete_order, and list_orders. It also notes required fields and variation handling, further clarifying the tool's scope.

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 usage context by stating line_items are required and advising to use variation_id for variable product variants. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to know when to choose this tool over update_order or delete_order.

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