bitrix_create_contact

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does add a useful non-obvious requirement: 'Требует confirm=true.' However, it does not describe side effects, response format, permissions, or behavior on duplicate contacts, which would be valuable for a write operation.

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 two short, purposeful sentences. It front-loads the action and object, then states the essential confirmation constraint. There is 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 an 8-parameter tool with no output schema and no annotations, the description covers the core operation and the confirmation gate. Still, it omits return value expectations and any additional behavioral context such as whether arrays are restricted or whether the operation creates a permanent record. It is adequate but not rich enough for a higher score.

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 coverage is 100% and every parameter has a Russian description, so the baseline is 3. The description adds semantic value beyond the schema by stating that the confirm parameter must be true, not merely present, which is critical for a successful call.

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 uses a specific verb ('Создать') and resource ('контакт в Bitrix24 CRM'), clearly indicating a create operation. It differentiates this tool from sibling contact tools like bitrix_update_contact, bitrix_list_contacts, bitrix_get_contact, and bitrix_find_contact.

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 intended usage is implied by the verb 'create': use this when a new contact needs to be created. However, the description does not explicitly state when to use it versus alternatives, nor does it mention any exclusions or prerequisites beyond confirm=true.

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