odoo_sales_create_order

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

No annotations are present, so the description carries the behavioral burden. It clearly states that the tool creates a sale.order with its lines, but it does not disclose the resulting order state (e.g., draft vs confirmed), permission requirements, or other side effects. The core mutation is transparent, but the broader behavioral context is thin.

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 brief, front-loaded with the purpose, and followed by a compact Args block that only includes necessary parameter details. There is no fluff or repetition of schema information.

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 tool with two required parameters, no enums, and an output schema available, the description covers the essential invocation details. It could be more complete with a note on the order state after creation or explicit usage routing, but nothing critical is missing for calling the tool correctly.

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?

With 0% schema description coverage, the description fully compensates by defining customer_id as the res.partner client ID and by giving the exact per-line structure with product_id and product_uom_qty. This adds essential meaning that the bare input schema does not provide.

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 uses a specific verb ('Crea') and resource ('cotización/pedido de venta (sale.order)') and mentions order lines, clearly distinguishing this from the purchase, project, and CRM creation siblings. It identifies both what the tool creates and the key included content.

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?

There is no explicit guidance about when to use this tool versus alternatives, no conditions for use, and no exclusions. The tool name and sibling list imply the sales domain, but the description itself does not route the agent toward this tool over odoo_purchase_create_order or the CRM/project creation tools.

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