Create contacts

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

With only openWorldHint annotation, the description adds useful behavioral context by noting bulk creation ('one or more') and the custom_fields_values format for phone/email. However, it does not disclose required fields, validation behavior, or response details. No contradiction with 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?

Two sentences, both concise and relevant. The first states the purpose, the second gives a specific API tip, with no filler or 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?

For a create tool with an open-ended schema and no output schema, the description omits essential information such as required contact fields (e.g., name), response format, error behavior, or a link to API docs. The phone/email tip is helpful but leaves the agent under-equipped for successful 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?

Schema description coverage is 0%, so the description partially compensates by explaining how to set phone/email via custom_fields_values. But it leaves other contact fields and the overall structure of each object unspecified, so the compensation is incomplete.

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 verb 'Create' and resource 'contacts', specifying 'one or more contacts', which distinguishes it from list/get/update siblings. The additional phone/email tip reinforces the tool's function without ambiguity.

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 contacts and provides a specific how-to for phone/email via custom_fields_values, but it does not explicitly state when to prefer this tool over alternatives like kommo_contacts_update, nor does it mention exclusions such as using lead creation tools for leads.

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