odoo_sales_list_orders

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

There are no annotations, so the description carries the behavioral burden. It does disclose filtering behavior and valid states, and 'Lista' implies a read-only operation, but it does not mention return format, pagination beyond limit, or any side-effect guarantees.

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 short, starts with the core purpose, and uses a clean Args list. No filler or redundant content appears.

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 simple, low-complexity list tool with no required parameters, the description covers the essential call semantics. It is complete enough to invoke correctly, though explicit usage guidance relative to siblings would make it fully 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?

Schema description coverage is 0%, so the description must compensate, and it does: each parameter is explained with meaningful guidance. Customer is tied to partner name, state lists valid values, and limit documents its default and meaning. This adds real value beyond the bare schema.

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 ('Lista') and the resource ('cotizaciones y pedidos de venta (sale.order)'). It is easy to distinguish from siblings like odoo_sales_create_order and odoo_crm_list_leads because it names the exact model and operation.

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 implies this is the tool to use for listing sales quotations/orders, and the sibling list shows a separate create tool. However, it does not explicitly state when to prefer this over related tools or provide any exclusion criteria.

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