odoo_execute

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

With no annotations, the description carries full burden. It discloses the read-only whitelist mechanism and names blocked write methods (create, write, unlink, etc.), providing critical safety context. It does not mention return format or post-enable side effects, but the core mutability guard is well covered.

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 two sentences, front-loaded with the purpose and followed by an essential safety constraint. There is zero redundant wording, making it optimally concise.

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 is broad and low-level, yet the description covers only the read/write gating and omits parameter syntax, examples, and guidance on when to choose this generic tool over dedicated siblings. The presence of an output schema mitigates return-value uncertainty, but for such a flexible tool the description remains incomplete.

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 input schema has 0% description coverage, so the description must explain the parameters. It only implies model and method but gives no guidance on the expected format for args and kwargs, which are strings (likely JSON). This leaves parameter usage ambiguous and uncompensated.

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 that the tool calls any method of an Odoo model via raw execute_kw, distinguishing it from specialized sibling tools like odoo_read or odoo_write. The verb 'Appeler' and resource 'méthode d'un modèle' are specific and unambiguous.

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?

It explains that in read-only mode a client-side whitelist applies, and write methods remain blocked until odoo_enable_write is called. This gives clear context for using the tool, though it does not explicitly mention when to prefer dedicated tools over this raw interface.

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