odoo_dashboard_list

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

With no annotations, the description carries the full burden, but it only states the basic listing behavior. It adds the detail that sections are included, which is useful, yet it does not mention whether an active connection is required, how results are ordered, or any potential limitations. The read-only nature is implied by 'Lister' but not explicitly disclosed.

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 a single, front-loaded sentence with no redundant wording. Every word contributes to the tool's purpose, making it appropriately concise and easy to parse.

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 no parameters and an output schema, the description covers the core purpose, but it omits usage guidance relative to sibling tools and any caveats about scope or prerequisites. It is minimally viable but lacks context that would help an agent choose it confidently.

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 tool has zero parameters, so the schema already fully defines the input. The description correctly implies that no arguments are needed, and no additional parameter explanation is required. This matches the baseline for a parameterless tool.

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 verb ('Lister' / list) and the resource ('tableaux de bord' / dashboards) plus their sections, which gives it clear scope. This distinguishes it from sibling tools like odoo_dashboard_inspect and odoo_dashboard_create, which imply inspection and creation respectively.

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 explicit guidance on when to use this tool versus alternatives such as odoo_dashboard_inspect or odoo_dashboard_create. Usage is only implied by the verb 'Lister' and the resource name, so an agent receives no context about appropriate scenarios or exclusions.

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