create_contact

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the preview/mutation dual behavior via the confirm parameter and the ability to set unmodeled fields via extra_values. It does not detail permissions, error handling, side effects, or what happens on success/failure beyond creation.

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 short (two sentences) with the first sentence front-loading purpose and key behavior. It is efficient, though the second sentence could be more specific about extra_values usage.

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 presence of an output schema (not shown), return values may be covered there. However, the description lacks details on behavior when confirm=False vs True, required fields beyond name, validation, and error scenarios. It is minimally adequate for creating a contact.

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%, so the description must compensate. It adds meaning to the confirm parameter (preview vs actual) and extra_values (fields not modeled), but does not describe email, phone, parent_id, is_company, or the format of extra_values. For 7 parameters, this is insufficient.

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 it creates a contact (res.partner) and mentions preview behavior. It differentiates from generic create_record by specifying the model, but does not explicitly contrast with siblings like create_lead or create_task.

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 that the tool can be used for preview (confirm=False) or immediate creation (confirm=True), and for setting extra fields via extra_values. However, it does not provide guidance on when to use this tool versus alternatives like create_lead or create_record, nor does it mention prerequisites or conditions.

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