Create order (quick order)

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

Beyond the annotations, the description reveals the default convert=true behavior, the need for product_id and billing_cycle_months, and the PRODUCTION warning that real billing documents are created. This adds valuable operational context not present in the annotations.

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?

Four concise, front-loaded sentences that each add distinct value: purpose, default behavior, product requirements, and production impact. No redundancy or filler.

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?

The description covers purpose, defaults, and production cautions, but does not mention return values or output shape, which is significant for a create tool lacking an output schema. Some parameter behavior is also ambiguous.

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?

The description adds meaning to selling_price ('overrides list pricing') and indicates billing_cycle_months is needed per product, but the schema only lists product_id as required, so this guidance is somewhat misleading. It adds some value beyond the 88% schema coverage but introduces potential confusion.

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 an order') via the admin quick-order flow, and clarifies its default conversion to invoice, distinguishing it from sibling tools like cancel_order or convert_order_to_invoice.

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 context (admin quick-order flow, default conversion behavior) but does not explicitly state when to use this tool versus alternatives such as convert_order_to_invoice, nor does it list exclusions.

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