odoo_create_record

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

The description reveals the non-obvious two-step behavior where the first call returns a proposal without creating anything, and execution only occurs on the second call with the token. This adds critical context beyond the annotations' simple mutation flag, and there is no contradiction with the annotations.

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 sentences, each serving a purpose: statement of function, explanation of the first step, and explanation of the execution step. It is concise with no redundancy.

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 of the human-approval flow, the description fully explains the protocol: what the first call returns, and what the second call requires. The presence of an output schema likely covers proposal details, so the description is complete for selection and invocation.

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 adds essential semantics for the 'approval_token' parameter, explaining its role in the two-step flow and requiring identical 'model'/'values' for execution. While 'model' and 'values' are not deeply elaborated, the token lifecycle is fully clarified, compensating for the 0% schema description coverage.

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 tool creates a record in an Odoo model, and specifies it is for write operations with human approval. This distinguishes it from sibling read/list tools by explicitly naming the write action and the approval requirement.

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 explicit usage guidance: call without 'approval_token' to obtain a proposal, then have a human resend with the token to execute. It also specifies that the model must be 'allowed for writing', giving a clear precondition for use.

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