odoo_create

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

With no annotations, the description carries the full burden. It discloses that exactly one record is created, returns the new ID, and warns that accounting documents need dedicated tools for correct line/tax/journal setup. It doesn't cover error handling or permissions, but for a generic create operation this is adequate behavioral detail.

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 three concise sentences: purpose, example, and usage guidance. Every sentence earns its place, with no filler or repetition. It is front-loaded with the core purpose first.

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 generic nature (any model), no output schema, and no annotations, the description provides a solid foundation: purpose, example, return value, and sibling disambiguation. It lacks error-handling details, but the core functionality is sufficiently covered for an agent to 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 0%, so the description must compensate. It does so with a concrete example: odoo_create("res.partner", {"name": "Acme LLC"}). This illustrates that 'model' is a string (e.g., res.partner) and 'values' is a dictionary of field values. This adds meaning beyond the raw schema fields.

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 the action: 'Create ONE record on any model' and specifies that it returns the new record's ID. This is a specific verb+resource combination that distinguishes it from sibling tools, especially since it explicitly contrasts with dedicated accounting tools.

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 gives explicit usage guidance: avoid for accounting documents, use dedicated accounting.* tools instead, and use this tool for 'anything they don't cover.' This directly addresses when to use and when not to use, naming specific alternatives.

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