update_records

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

Discloses the preview/write behavior (dry-run unless confirm=True), which is critical for an update tool. No annotations provided, so description carries full burden; it clearly explains the mutation and confirmation mechanism.

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?

Extremely concise; uses structured Args format with clear bullet points. Every sentence adds value. No unnecessary words.

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?

Covers core functionality, parameters, and preview behavior. Includes constraint on model. Does not mention potential errors or limitations (e.g., validation of values). Output schema exists, so return values are not required.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's meaning: model must be in writable models, ids are record IDs, values is field mapping, and confirm controls dry-run.

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?

Clearly states it updates records, can update one or more, and distinguishes from sibling tools like create_record and delete_records. The description uses specific verb 'update' and resource '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?

Provides context about when to use (updating records) and a constraint (model must be in ODOO_WRITABLE_MODELS), but does not explicitly state when not to use or compare to alternatives.

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