bx24_marketing

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

With no annotations, the description carries the full behavioral burden, yet it only lists method names and resources. It does not disclose side effects such as email sending, potential destructive segment operations, or confirmation/authorization requirements.

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 reasonably short but reads as a keyword dump rather than structured prose, and the bilingual RU/EN list adds length without much operational value. The core capabilities are front-loaded, so it is still serviceable.

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 multi-action tool with 10 parameters and no output schema or annotations, but the description does not map actions to their relevant parameters, prerequisites, or return behavior. The schema's enum explanations help, but the description leaves important invocation context to be reverse-engineered.

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%, so the input schema already documents all 10 parameters and the action enum. The tool description adds no parameter-level meaning, keeping this at the baseline for well-covered schemas.

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 enumerates the tool's domain and capabilities: segments from CRM, broadcast send, lead filtering, and trade platforms, and it names the underlying Bitrix24 REST methods. It is more than a tautology, though it does not explicitly distinguish itself from overlapping siblings such as bx24_mail or bx24_crm_leads.

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 phrase 'Bitrix24 marketing' and the listed operations imply when the tool is appropriate, but there are no explicit when/when-not statements or alternatives. An agent must infer that this is the marketing-focused counterpart to general mail and CRM lead tools.

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