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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the destructive nature is covered structurally. The description adds genuinely non-obvious context beyond that: the return shape (model, ids, updated) and, importantly, that when write confirmation is enabled nothing is actually changed and a pending-action code comes back instead. It still omits what happens on partial/invalid field sets and whether the update is atomic, which keeps it below a 5.

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 tight sentences ordered by importance: what it does first, the confirmation-mode caveat second. No filler, no restatement of the title, and the surprising behavior is surfaced rather than buried.

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?

An output schema exists, so return values need only light treatment and the description supplies the key nuance about the pending-action variant. For a destructive mutation on a nested, free-form 'values' object, it would be stronger if it warned about invalid field names or required write access, but the essentials for correct invocation are present.

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 100%, so 'model', 'ids' and 'values' are already documented in the schema, establishing the baseline of 3. The description only says 'with the given field values', adding no format, validation, or model-specific detail beyond what the schema already conveys.

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?

States a specific verb and resource: 'Updates existing Odoo records with the given field values.' The verb 'updates' cleanly separates it from odoo_create and odoo_unlink in the sibling list, though no sibling is named explicitly.

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?

Usage is only implied by the word 'existing' – an agent can infer this is for modifying records that already have IDs rather than creating them. There is no explicit when-to-use/when-not guidance, no mention of odoo_create as the alternative for new records, and no prerequisites such as required permissions on the target model.

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