bx24_crm_contacts

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

With no annotations, the description carries the full behavioral burden, but it only offers the broad labels 'CRUD' and 'company bindings'. It does not disclose that delete/unbind/clear actions are irreversible, that destructive actions may require a confirm flag, or what side effects or response shapes to expect. The destructive labels in the input schema help, but the description itself stays silent on these traits.

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 front-loads the resource and core capabilities in one compact sentence, then adds method-group and locale hints. The RU/EN keyword fragment adds modest value for multilingual queries but is slightly tangential; overall the text is efficient and appropriately sized.

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 13-parameter/18-action surface is complex, and the high-level description alone would not be enough. The rich input schema compensates for most gaps, but with no output schema and no return-value description, an agent must infer response shapes from action names and the fields object. That leaves a noticeable but not critical gap.

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?

Input schema coverage is 100%, so the baseline of 3 applies; the description contributes no parameter-level detail. The schema's action enum and field descriptions carry the semantics, which is adequate.

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 names the exact Bitrix24 resource ('CRM contacts') and lists the operation families it covers: CRUD, company bindings, and user fields. This distinguishes it from siblings like bx24_crm_deals and bx24_crm_companies and maps directly to the crm.contact.* REST method groups.

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?

Usage is implied by the resource name and operation families: it is the tool for contact-related actions. However, it never explicitly states when to use it versus sibling tools or which sibling covers adjacent entities (e.g., bx24_crm_companies for company-only operations), so the guidance is implicit rather than prescriptive.

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