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

Annotations already declare destructiveHint=true, and the description reinforces this with 'DESTRUCTIVO' and 'permanentemente', adding minor context about irreversibility. However, it does not disclose potential cascading effects or any other behavioral nuances beyond the destructive flag.

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 extremely concise, using just two short sentences to convey the purpose and destructive nature. It is front-loaded with the action and warning, with no wasted 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?

For a simple delete operation, the description covers the essential purpose. With schema covering parameters, an output schema present, and annotations indicating destructiveness, the description is sufficient for an agent to understand the tool's core function, though it omits any mention of return values or side effects beyond what is structured.

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 both parameters ('IDs a eliminar' and 'Modelo Odoo') already documented in the schema. The description adds no additional meaning or detail beyond what the schema provides, so the baseline of 3 applies.

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 the verb 'Elimina' (deletes) and the resource 'registros' (records), and adds 'permanentemente' to specify irreversibility. This distinguishes it from siblings like odoo_create, odoo_write, and odoo_read, which perform different operations.

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 is given on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or exclusions. The description simply states the action without context on when it should be invoked.

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