create_record

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

With no annotations, the description takes full responsibility. It discloses that the tool can either preview or actually create based on confirm, and that the model must be writable. This provides clear behavioral expectations, though it could explicitly state that it performs write operations.

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 extremely concise: two sentences plus a bulleted list of parameters. Every sentence adds value, and the structure (overview then args) is clear.

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 complexity (3 params, no annotations, but output schema exists), the description covers the core behavior: creation with preview option, model constraints, and parameter details. It doesn't describe the return format of preview, but the output schema (unseen) likely covers that.

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 0%, so the description must compensate. It adds meaning: model must be in ODOO_WRITABLE_MODELS, values is a field-value mapping, and confirm toggles between preview and actual creation. This is far beyond the schema's basic type 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 clearly states 'Create one record' and explains the preview versus actual creation via confirm parameter. It distinguishes itself from sibling tools like create_contact or create_lead by being generic, covering any Odoo model.

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 implies usage for creating any record in ODOO_WRITABLE_MODELS and mentions a dry-run mode, but does not explicitly compare with siblings or state when not to use this tool versus specific creators like create_contact.

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