odoo_purchase_list_orders

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

No annotations are provided, so the description carries the burden. It does disclose key behaviors: filters by supplier and state, and defaults to 20 records via limit. It does not mention ordering, pagination, or explicitly state the read-only nature beyond the 'Lista' verb.

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, front-loaded with the core purpose, and uses a clear argument list. Every sentence adds useful information and there is no fluff.

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 listing tool with an output schema and three well-documented parameters, the description is largely complete. The main gap is lack of explicit guidance on when to select this tool over sibling list tools.

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%, but the description documents all three parameters meaningfully: supplier filters by name, state lists all allowed values, and limit specifies the maximum records with default 20.

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 states 'Lista órdenes de compra (purchase.order)', which clearly identifies the verb and resource. It does not explicitly differentiate from sibling tools, but the resource and name make the purchase domain obvious.

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 usage through the purchase.order context and filter arguments, but it does not explicitly state when to use this tool versus sibling listing tools like odoo_sales_list_orders or odoo_crm_list_leads.

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