tiendanube_create_order

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

With no annotations provided, the description carries the full burden. It discloses that the tool supports custom pricing, shipping options, payment gateway selection, and inventory management, giving the agent a good sense of its behavioral capabilities. However, it does not mention rate limits, authorization needs, or idempotency, which would be needed for a 5.

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 a single sentence that front-loads the action with an emoji and 'CREATE NEW ORDER'. It conveys the purpose, use cases, and requirements efficiently. It could be broken into shorter sentences for readability, but it remains clear and concise.

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 high parameter count (33) and no output schema, the description covers the essential required fields and supported features. However, it lacks mention of optional parameters like shipping address fields, payment status enumeration, and what the tool returns (output). This leaves some gaps for an agent to fully understand the tool's capabilities.

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 coverage is 100% (all parameters described in the schema). The description adds context by summarizing required fields (customer name/email, products, billing address) and supported features (custom pricing, shipping). However, it does not provide new details beyond what is already in the schema, meeting the baseline but not exceeding.

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 verb 'Create' and the resource 'new order', and explicitly lists use cases such as manual order creation, bulk imports, external integrations, and processing orders from other channels. This distinguishes it from sibling tools like update_order or cancel_order, as it focuses on creation of a new order.

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 explicit when-to-use scenarios (manual creation, bulk imports, etc.) and lists required inputs (customer details, product variants, billing address). However, it does not explicitly mention when not to use the tool or reference alternatives, which prevents a 5.

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