odoo_stock_mo_delete_draft

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

Describes bypassing Odoo's ORM constraints via raw SQL and ir.actions.server. Details cascade deletion of stock.moves and procurement.group. With no annotations, this description fully informs about destructive behavior.

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?

Concise single paragraph, every sentence adds value. No redundancy, front-loaded with action and key conditions.

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?

Covers behavior, preconditions, and safety advice. Lacks output/return value description, though for a delete tool the action itself is primary. Reasonably complete given the complexity.

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 covers 2 of 3 params with descriptions; connection lacks description. The description adds value by emphasizing dry_run usage, but could be more explicit about connection parameter meaning.

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?

Clearly states the verb (DELETE) and specific resource (draft or cancelled mrp.production) with cascade deletion details. Distinguishes from generic siblings like odoo_unlink.

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?

Explicitly advises to use dry_run=true first, and lists refusal conditions (has SVL, stock.move with qty>0, already-done state). Provides clear when-to and when-not-to use.

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