odoo_create

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

Annotations already indicate this is not read-only and not idempotent. The description adds useful context by stating the operation runs under configured Odoo user permissions, which implies authorization constraints. No contradiction with annotations, but it does not disclose return values, validation behavior, or side effects beyond creation.

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 single sentence that is front-loaded with the key action and object. Every word earns its place, and the permission context is concise rather than redundant.

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?

The description is minimally adequate for an agent to understand the tool creates an Odoo record with the given model and values. However, with no output schema, it does not explain what the tool returns, such as the created record ID, nor does it address required-field handling or error behavior. These are clear gaps.

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?

The description does not explain the 'values' parameter beyond what the schema already shows. The schema documents 'model' but leaves 'values' with only a generic object type. Since schema description coverage is only 50%, the description should compensate, but it does not clarify that values are the field-value mapping for the new record.

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 uses a specific verb and resource: 'Create a record in an Odoo model.' This clearly distinguishes the tool from siblings like odoo_write, odoo_unlink, and odoo_search_read by the operation it performs.

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 makes it clear the tool is for creating records, which is a clear usage context. However, it does not explicitly state when not to use it or mention alternatives such as odoo_write for updates, so it stops short of full routing guidance.

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