create_record

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

Annotations already indicate not destructive. The description adds return value (ID of new record). However, it does not disclose potential side effects (e.g., triggering workflows) or permission requirements beyond 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 highly concise: one sentence of purpose, then structured Args and Returns sections. Every line adds value 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 simple input schema (two parameters) and presence of an output schema, the description covers the core semantics. It could mention that the model must exist, but overall it is sufficient for a create operation.

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 adds crucial meaning: explaining 'model' as an Odoo model name with example, and 'values' as a dict of field-value pairs. This compensates well for the sparse schema.

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's action: 'Create a new record in an Odoo model.' It provides specific examples and distinguishes it from siblings like read_record, update_records, and delete_records by focusing on creation.

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 new records but does not explicitly differentiate when to use vs. alternatives (e.g., update_records for existing records). No guidance on when not to use or prerequisites.

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