odoo_purchase_create_order

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool creates a purchase.order, but it does not mention side effects, required permissions, validation behavior, idempotency, or what happens on failure. For a mutation tool, this is a notable transparency gap.

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 compact and front-loaded: the first sentence states the core action, and the second section documents parameters without filler. Every sentence provides useful information, and the parameter examples are directly actionable.

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 bare schema and absent annotations, the description supplies the essential input semantics needed to call the tool correctly. It does not mention prerequisites like the supplier needing to exist or product validation, but an output schema exists and the described inputs are sufficient for a basic creation call.

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 schema provides only parameter names and types with 0% description coverage, but the description fully compensates. It documents supplier_id as the res.partner provider ID and order_lines as a list of dicts with product_id, product_qty, and price_unit, including type hints for each field.

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') with a specific resource ('orden de compra (purchase.order)') and explicitly states it creates the order with its lines. This clearly distinguishes it from listing tools like odoo_purchase_list_orders and creation tools in other domains like odoo_sales_create_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 states what the tool does but does not explicitly say when to use it versus alternatives or when not to use it. The tool name and sibling list imply it is for creating purchase orders, but no exclusionary guidance or alternative routing is provided in the description itself.

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