create_order

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it returns '{success, id, order?}', but does not elaborate on side effects, idempotency, or error cases. Thus it adds some value beyond annotations but not substantial behavioral detail.

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: first covers the core action and customer linking decisions, second provides return format. No redundant information. Highly efficient.

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, 1 required, and no output schema, the description covers the critical decision logic (customer handling) and return shape. Schema covers remaining param details. Could mention items requirement, but it's inferred from the main action. Good for the complexity level.

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%, providing baseline 3. The description adds meaning by explaining the two mutually exclusive customer linking modes and which parameters to use together (customer_id/external_id vs first_name+phone/email). This goes beyond schema descriptions.

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 'Create an order with line items and delivery', specifying the verb (create) and resource (order). It distinguishes from sibling tools like update_order by focusing on creation and customer linking methods.

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 explains when to use each customer linking method (existing vs inline creation). While it doesn't explicitly exclude alternative tools like create_customer, the context is clear for order creation. No explicit when-not guidance, but the sibling tools are distinct actions.

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