odoo_write

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that updates existing records, but omits side effects (permanence), permissions, validation, or return behavior. This is thin for a mutation tool.

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, short sentence with no wasted words. However, it is under-specified; it earns its place as a brief summary but lacks structure or detail, making it minimally viable but not efficiently informative.

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 a generic write operation with three required parameters, nested objects, no output schema, and no annotations. The description only covers the basic action, failing to explain parameter semantics, return values, or usage constraints. This is inadequate for correct invocation in most 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?

Schema description coverage is 0%, and the description adds minimal value: it mentions 'field values' (relating to 'values') but does not explain 'model' or 'ids'. The agent must infer that 'ids' are record identifiers and 'model' is the target Odoo model, which is not explicitly stated.

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 tool updates existing records with field values, using a specific verb and resource. It distinguishes itself from odoo_create and odoo_unlink, though it doesn't explicitly position itself relative to specialized update tools like update_invoice.

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 is provided on when to use this tool versus alternatives. The description mentions no context, prerequisites, or exclusions, leaving the agent to infer usage from the generic 'update' verb.

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