odoo_stock_product_flip_to_storable

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

Describes key behaviors: bypasses ORM constraint via raw SQL, inserts stock.quant directly without duplicate SVL, existing SVLs stay intact, returns full pre/post snapshot. Since no annotations exist, description carries full burden and covers critical traits, though it could detail the snapshot structure or error conditions.

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 a focused paragraph that front-loads purpose, then explains mechanism, use case, and precaution. No unnecessary words; every sentence adds value.

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 the tool's complexity, detailed parameters, and lack of output schema, the description sufficiently covers purpose, behavior, usage, parameters, and return value. It is complete for an agent to select and invoke correctly.

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 high (86%), and description adds extra context for parameters like location_id ('usually GRN destination'), quantity ('must match existing SVL remaining_qty'), and in_date ('Should match GRN date'). This goes beyond the schema definitions.

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 states a specific verb ('Flip') and resource ('product from consumable to storable'), and distinguishes from siblings by detailing a unique operation (bypassing ORM constraint, direct quant insertion). No sibling tool performs this action.

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?

Provides explicit usage context: 'Use when a GRN/bill was recorded for a product that was mistakenly set as consu.' Includes a mandatory precaution: 'ALWAYS use dry_run=true first to preview impact.' This gives clear guidance on when and how to use.

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