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

Annotations already declare readOnlyHint=false and destructiveHint=true, yet the description adds genuinely new behavior: the write-confirmation gate can turn a delete into a no-op returning a pending-action code. That is exactly the kind of side-effect an agent needs to know. It stops short of saying what happens to related records or how partial failures are reported.

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 sentences, no filler, with the permanence warning and the return shape front-loaded before the conditional confirmation behavior.

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?

Output schema exists so return values need not be explained, and annotations carry the safety profile. The description closes the remaining meaningful gap by disclosing the confirmation-gated non-deletion path. Only edge-case behavior on errors or record dependencies is left unaddressed.

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 coverage is 100% and both parameters (ids, model) are documented in the schema, so the baseline of 3 applies. The description adds nothing about batch semantics, model naming format, or what happens with invalid ids.

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 ('Permanently deletes Odoo records') and adds the permanence qualifier, which separates it from reversible mutations like odoo_write. It does not name a sibling explicitly, so differentiation is inferred rather than stated.

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?

There is no guidance on when to choose this over odoo_write, odoo_cancel or odoo_confirm, nor any prerequisites such as required model access. Usage context is only implied by the tool name and the destructive framing.

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