create_store_order

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds context about idempotency (unique order_id) and creation behavior, but does not disclose any further side effects or failure modes. Adequate but not exceptional.

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 concise: a few sentences and a bulleted args list. It front-loads the purpose and then details. Efficiently uses space, though the return type mention could be integrated; still good.

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?

Given the tool's complexity (6 params, nested objects, many siblings) and presence of output schema, the description covers essential usage. It explains prerequisites, parameter requirements, and return format. Could include more on error handling, but overall complete.

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?

Despite 0% schema description coverage, the description explains each key parameter: store_id, order_id, customer, lines, additional_fields. It adds constraints like 'client-supplied and must be unique', 'customer must include id', and 'lines require id, product_id, product_variant_id, quantity, price'. The account parameter is omitted but optional with default.

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 e-commerce order in a store with a customer and line items'), specifying the verb, resource, and scope. It distinguishes this tool from siblings like create_store_cart and create_store_customer.

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?

Provides explicit guidance: explains when to use manual commerce vs automated integrations (Shopify/WooCommerce), notes that order_id must be unique and customer must already exist or be provided with required id, and directs to list_ecommerce_stores for store_id. Missing explicit when-not-to-use but sufficient.

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