odoo_unlink

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

With no annotations, the description carries the full burden. It discloses irreversibility ('CANNOT BE UNDONE'), the disabled-by-default behavior, the required environment variable to enable, and a specific behavioral contrast (accounting reversals). This is exceptional transparency for a destructive operation.

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 concise and well-structured. The first sentence states the action and danger, the second explains why it's disabled, and the third gives the configuration. Every sentence serves a purpose, and it is front-loaded with the critical 'permanently delete' warning.

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 that this is a delete tool with no output schema, the description covers the essential context: irreversibility, opt-in activation, and a usage warning. It lacks details on return values or error handling, but those are less critical for deletion, and the safety/config context is fully addressed.

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 description does not explicitly describe the 'model' or 'ids' parameters. It only implies that 'ids' refers to records being deleted, but provides no detail on what model names are valid or the type of IDs. With 0% schema coverage, the description fails to compensate adequately.

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 'Permanently delete one or more records' with a strong verb (delete) and explicit target (records). This distinguishes it from sibling tools like odoo_write (update) and odoo_create (create), making its purpose unambiguous.

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?

It specifies that deletion is permanent and disabled by default, and contrasts with reversible accounting entries that should be reversed instead. This gives clear context for when to use the tool, though it doesn't name explicit alternative tools for deletion.

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