commerce_order_createCreate a new Drupal commerce order by specifying a store ID and order ID, with optional items, billing profile, and order type.
Create a new commerce order.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| items | No | ||
| store_id | Yes | ||
| order_type | No | default | |
| billing_profile | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses only that an order is created; it says nothing about permission requirements, whether the id is client-supplied or generated, what happens to existing records, or idempotency. For a mutation tool with zero annotation coverage this is a significant gap.
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?
A single short sentence with no waste, but it is under-specified rather than concise; the brevity leaves required context unstated. Adequate structure, insufficient 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?
An output schema exists so return values need no explanation, but for a 5-parameter mutation with 0% schema coverage and no annotations, the description is far too thin. An agent cannot determine required inputs, field formats, or side effects from this text.
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% across 5 parameters, and the description adds no meaning for any of them. It does not explain what 'id' represents (order ID vs external ID), the shape of 'items', the allowed 'order_type' values, or the 'billing_profile' object.
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?
States a specific verb ('Create') and resource ('commerce order'), so the agent knows exactly what operation is being performed. However, it does nothing to distinguish itself from siblings like commerce_order_get, commerce_order_update, or commerce_order_list.
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 the many sibling order tools, no prerequisites (e.g., store must exist), and no exclusions. The agent must infer everything from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.