create_order

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't disclose important behavioral traits like: what permissions are needed, whether the order is saved immediately or temporarily, what happens on failure, or if there are rate limits. It mentions the order type options but doesn't explain their implications.

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 extremely concise with just two short sentences that are front-loaded with the main purpose. Every word earns its place - the first sentence states what the tool does, and the second provides important workflow context without redundancy.

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 mutation tool with 9 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., does it return an order ID?), error conditions, authentication requirements, or how this tool relates to the complete ordering workflow with siblings like 'place_order' and 'add_item_to_order'.

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 schema already documents all 9 parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'delivery or carryout' which relates to the 'order_type' parameter, but doesn't provide additional semantic context about parameter relationships or business logic.

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 clearly states the action ('Create a new order') and resource ('order'), specifying it's for 'delivery or carryout'. It distinguishes from siblings like 'add_item_to_order' by noting it's 'Required before adding items', but doesn't explicitly differentiate from 'place_order' which might be a finalization step.

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 some contextual guidance by stating this tool is 'Required before adding items', which implies it should be used early in the ordering workflow. However, it doesn't explicitly state when to use this versus 'place_order' or other order-related tools, nor does it mention prerequisites or exclusions.

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