create_crm_customer

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

No annotations are provided, and the description only marks the tool as [mutation]. It does not disclose side effects (e.g., duplicate handling, required permissions, or system impact). The description adds minimal behavioral insight beyond the mutation hint.

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 a single, front-loaded sentence with no unnecessary words. It is concise, but could be more informative within the same space, e.g., by including the scope (individual vs bulk). Minor improvement possible.

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 large set of sibling tools, the description lacks context about what this tool produces (e.g., does it just create a CRM entry? Is there any return value?). It does not explain 'CRM interno de WAzion' or confirm if it's a single contact addition. Incomplete for the environment.

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 100% schema description coverage, the schema already documents the single parameter (whatsapp_number) with format details. The description adds no extra meaning or usage nuance beyond 'creates a new contact', so it meets the baseline but does not exceed.

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 new CRM contact in the internal WAzion CRM. It uses a specific verb ('Crear') and resource ('contacto CRM'). However, it does not differentiate from siblings like import_crm_contacts or add_contacts_to_list, preventing a top score.

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 no guidance on when to use this tool versus alternatives, such as import_crm_contacts or create_contact_list. No prerequisites, exclusions, or context are given, leaving the agent to guess the appropriate scenario.

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