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

Annotations are sparse: only readOnlyHint=false, indicating write operation. The description confirms update but doesn't disclose additional behaviors like whether it overwrites fields, requires specific permissions, or handles partial updates. With minimal annotations, the description should carry more weight but doesn't provide depth.

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?

It's a single short sentence, exceedingly concise, but it under-specifies. Being concise is good, but it's almost too minimal to be useful. It front-loads the action but lacks any elaboration, so it's not well-structured for an agent to grasp context.

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 moderate complexity with an output schema and nested objects, the description is incomplete. It doesn't mention expected behavior on failure, authentication requirements, or how the output is structured. Sibling tools like odoo_execute could overlap, and without usage guidance, an agent may not know when this is the right choice.

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%, with descriptions for model ('Modelo Odoo'), ids ('IDs a actualizar'), and values ('Valores a establecer'). The description adds no extra meaning beyond that, but since coverage is high, baseline 3 is appropriate. The 'values' object is generic and the description doesn't add specifics about field formats or update semantics.

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 'Actualiza registros existentes' clearly states it updates existing records, with a specific verb and resource. It distinguishes from create/unlink but doesn't differentiate from other update-like operations like odoo_execute or odoo_search_read. Minimal but adequate.

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 on when to use this tool versus alternatives. While the verb 'Actualiza' implies writing, there's no mention of when to prefer this over odoo_execute for updates, or any exclusions. The context is minimal and doesn't help routing.

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