odoo_write

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

With no annotations, the description carries the full burden. It discloses the write-lock gating behavior and the modification nature, which is useful. But it omits other behavioral aspects like reversibility, permission requirements, or side effects on existing fields.

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?

Two concise sentences front-load the action and include a necessary warning about the write lock. No wasted words; the structure is clean and easy to scan.

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?

Given the tool's complexity (3 required params) and the presence of an output schema, the description covers the core action and a key constraint. The `model` parameter is fairly obvious in an Odoo context, and the output schema handles return value details, making it sufficiently complete.

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 coverage is 0%, so the description must compensate. It explains that `ids` is a JSON array and `values` is a JSON object, adding structure beyond the plain string schema. The `model` parameter is left undocumented, so only two of three parameters gain semantic clarity.

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 'Modifier des enregistrements' (modify records), a specific verb+resource. It distinguishes from create/unlink but not from odoo_update_where, though the explicit `ids` parameter suggests a direct update by ID.

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 an explicit prerequisite: blocked until odoo_enable_write is called. However, it gives no guidance on when to use this tool over odoo_update_where or odoo_upsert, so usage context is only partially covered.

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