odoo_unlink

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

Annotations already mark the tool as destructive, and the description aligns by saying 'Permanently delete.' It adds useful context beyond annotations: the deletion is permanent and subject to the configured Odoo user's permissions, which clarifies that permission failures are possible.

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 entire description is one front-loaded sentence: it starts with the core action 'Permanently delete' and then states the object and permission context. There is no filler or redundant restatement of the schema.

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 two-parameter destructive tool, the description covers the essential behavior, permanence, and permission context. The annotations further supply destructive and non-read-only hints, and no output schema exists, so missing return-value details are not a major gap for an agent selecting and invoking this delete tool.

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?

The schema documents 'model' as a technical Odoo model name, but 'ids' lacks a description. The phrase 'one or more Odoo records' helps clarify that 'ids' refers to the target record identifiers, but it does not add much beyond what the schema and parameter names already imply. With only 50% schema description coverage, this partial clarification is adequate but not rich.

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 states a specific verb ('delete') and resource ('Odoo records') with a clear destructive scope. It also differentiates itself from siblings like odoo_create, odoo_write, and odoo_search_read by uniquely indicating a deletion operation.

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 use case is implied by 'Permanently delete one or more Odoo records,' but the description does not explicitly state when to prefer this tool over alternatives or mention any when-not conditions. It relies on the reader to infer that this is the deletion counterpart to create/write/search operations.

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