Run Odoo workflow action

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

Annotations already declare destructiveHint=true, so the tool is known to be destructive. The description adds 'Requires confirmation' which is useful, but it does not explain what 'confirmation' means (e.g., user prompt or a confirmation parameter), what the destructive effect is, or whether changes are reversible. For a destructive mutation tool with no additional annotation context, this is insufficient.

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 concise, a single sentence, and starts with the main purpose. It avoids extraneous information. It could be structured slightly better by front-loading the confirmation requirement, but overall it is efficient.

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?

The tool has a complex purpose (workflow actions on Odoo) with no parameter documentation and no behavioral detail beyond the annotation. The output schema exists, so return values are not needed, but the description still omits critical usage context like the meaning of 'confirmed' and the destructive side-effects. It is not complete enough for an agent to call it correctly without external knowledge.

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%, and the description does not describe any of the four parameters. The schema provides basic names and types, but no meaning (e.g., what 'model' values are valid, what 'action' options exist, and how 'confirmed' relates to the confirmation requirement). The description must compensate for this gap, but it does not.

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 ('Execute') and resource ('business workflow action on Odoo records') with a concrete example ('confirm a sale order'). It is distinct from sibling tools like aidoo_workflow_run, but does not explicitly differentiate itself from similar workflow tools.

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?

No guidance on when to use this tool versus siblings like aidoo_workflow_run or aidoo_workflow_list. The example gives a hint of typical use, but it does not state when not to use it (e.g., read-only operations should use aidoo_read).

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