odoo_write

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

Annotations already provide the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds context about permissions, but does not disclose other behavioral aspects such as error handling, side effects, or what happens when IDs do not exist.

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 sentence with no redundant words. It is succinct and front-loads the primary action clearly.

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 write operation with no output schema, the description is minimal. It does not explain return values, error behavior, maximum batch limits, or the effect of the idempotency hint. It relies on annotations for safety but lacks operational context for an agent to invoke it correctly in complex scenarios.

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?

Only 33% of parameters (model) have schema descriptions. The description implicitly connects 'ids' to 'one or more records', but provides no detail about 'values' or the relationship between parameters. It does not compensate for the low schema coverage.

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 specific verb 'update' and resource 'Odoo records', which naturally differentiates it from sibling tools like odoo_create (create) and odoo_unlink (delete). It also specifies the scope with 'one or more records'.

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 usage is implied by the verb 'update' (modifying existing records), and the context of using an Odoo user permissions is mentioned. However, there is no explicit guidance on when to prefer this over odoo_create or odoo_unlink, nor are alternatives or exclusions named.

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