Delete Record

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description adds the irreversibility emphasis and, more importantly, the two-phase confirmation workflow that the annotations do not encode. It stops short of noting Odoo access-right requirements or cascade/error behavior, so it is not fully exhaustive.

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?

Front-loaded with the purpose and risk in one line, then the operational rule in the following lines. Every sentence carries a distinct constraint (what it does, that it cannot be undone, how to sequence the calls) with no filler.

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?

An output schema exists so return values need not be described, and annotations carry the destructive/idempotent profile. Combined with the fully documented 3-parameter schema, the description supplies exactly the missing piece an agent needs: the confirm-before-delete workflow.

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%, so the schema already documents ids, model and the confirm safety flag, giving a baseline of 3. The description adds meaning by attaching hard ordering semantics to confirm (False first, True only after approval), which constrains how the parameter must be used in a sequence rather than just what it stores.

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 ('Delete records from an Odoo model') and immediately flags the operation as IRREVERSIBLE, which cleanly separates it from create_record and update_record in the sibling set. An agent can identify the tool without opening any schema.

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?

Gives an explicit, mandatory protocol: call with confirm=False first, set confirm=True only after explicit user approval, never on the first call. This is unambiguous when-to-use guidance with exclusions ('NEVER') rather than soft suggestion.

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