odoo_project_list_projects

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

No annotations are present, so the description carries the behavioral disclosure burden. It does add useful behavior: name filtering is a partial search, and limit caps the number of returned records with a default of 20. However, it does not mention ordering, pagination, empty-result behavior, or explicitly state read-only semantics beyond the word 'Lista'.

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 and front-loaded with the operation, followed by a compact Args list. Every sentence adds value; there is no repetition or unnecessary detail.

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 list tool with two optional parameters and an output schema, the description covers the core call behavior and parameter semantics sufficiently. Return-value explanation is not needed because an output schema exists. The only notable gap is usage-vs-alternatives guidance, which is already scored separately.

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 JSON schema has no descriptions, so the parameter semantics fall entirely on the tool description. It compensates by explaining that name is a partial project-name filter and limit is the maximum records to return. It adds meaning beyond the bare schema types, though the default of 20 is already present in the 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 opens with 'Lista proyectos (project.project)', which clearly states the action (list) and the resource (Odoo project model). It is distinct from sibling tools like odoo_project_list_tasks, odoo_crm_list_leads, and odoo_sales_list_orders because the resource is explicitly projects.

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 no guidance about when to use this tool versus alternatives such as odoo_project_list_tasks or the CRM/sales list tools. It only states what the tool does and describes its parameters. There are no prerequisites, exclusions, or explicit use-case scenarios.

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