Create Odoo records

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

Annotations already indicate a non-read-only, non-idempotent operation. The description adds the requirement for confirmation, which is a behavioral trait not captured in the annotations. It does not contradict any annotations and provides useful operational context.

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 two sentences with no fluff. It front-loads the core purpose and then gives concise usage and confirmation details. Every word earns its place.

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?

While the description covers the main creation modes and confirmation, it leaves ambiguity about how 'confirmed' is used (does the agent need to set it true?) and what happens if both 'values' and 'values_list' are provided. The output schema exists but is not shown; given the tool's complexity, more detail on parameter interplay would improve completeness.

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?

With 0% schema description coverage, the description must compensate. It explains the roles of 'values' and 'values_list' and alludes to 'confirmed' via 'Requires confirmation', but it does not detail the 'model' parameter or clarify the relationship/mutual exclusivity between 'values' and 'values_list'. Partial compensation only.

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 'Create one or multiple records in an Odoo model' with a specific verb and resource, and distinguishes between single and batch creation via 'values' and 'values_list'. It is immediately distinguishable from sibling tools like aidoo_read, aidoo_write, and aidoo_delete.

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?

The description provides clear parameter-level guidance ('Use values for a single record, or values_list for batch creation') and mentions the confirmation requirement. However, it does not explicitly name alternatives or state when not to use this tool, though the create vs. write/delete distinction is implied.

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