bx24_openlines

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not mention side effects, write operations, permissions, rate limits, or state changes, even though actions like config_add, config_update, network_join, and crm_lead_create are clearly mutating. The phrase 'Methods imopenlines.*' identifies an API family but not the behavioral consequences.

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 and front-loads the core domain. The RU/EN terminology mapping adds marginal value but is not excessive. It reads as a compact overview rather than an explanation, though no sentence is wasted.

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?

This is a 12-action tool with nested objects and no output schema, yet the description offers no workflow context, return-value hints, or operation-specific guidance. The input schema documents each parameter, but the description does not help an agent reason about how actions differ, which parameters apply to which action, or what results to expect.

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 100%, and every parameter already has a meaningful description, so the baseline is 3. The tool description itself adds no parameter-level detail beyond what the schema already provides. There is no need for the description to compensate here.

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 identifies the Bitrix24 IM open lines subsystem and lists its main subdomains (configs, sessions, dialogs, operators, CRM links, network), which is clear and distinct from general IM or CRM tools. It lacks a single specific verb+resource, but the action enum provides concrete operation names. It does not explicitly contrast itself with siblings like bx24_im or bx24_im_chat, though the domain is reasonably clear.

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?

No guidance is given about when to use this tool versus related alternatives such as bx24_im, bx24_im_chat, or the CRM tools. The domain label 'IM open lines' implies a particular context, but there are no stated exclusions, prerequisites, or selection criteria. The action enum lists operations, but the description does not explain which scenario maps to which tool.

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