odoo_crm_create_lead

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

With no annotations, the description carries the burden of behavioral disclosure. It states the core creation behavior but does not mention side effects, permission requirements, idempotency, duplicate handling, or any operational nuance. This is a thin description for a mutation tool.

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 concise and front-loaded with the purpose, followed by a clean structured Args list. Every sentence earns its place and there is no irrelevant filler.

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 tool is simple and has an output schema, and all parameters are described. However, without annotations, the lack of behavioral guidance such as expected side effects, prerequisites, or errors leaves it only minimally complete 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?

Schema description coverage is 0%, but the description compensates by documenting all six parameters with meaningful Spanish semantics, including the required field, the type_ values, and the optional revenue/contact fields. It adds value beyond the bare 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 identifies the action ('Crea un nuevo lead u oportunidad') and the resource ('CRM de Odoo'). This distinguishes it from siblings like odoo_crm_update_lead and odoo_crm_list_leads by specifying creating a new record.

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?

It is implied that this tool should be used when creating a new lead or opportunity, but no explicit alternatives or exclusion conditions are mentioned. The description does not contrast it with odoo_crm_update_lead or list tools.

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