bitrix_add_project_members

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 mentions that confirm=true is required, which is useful, but it does not disclose permissions needed, side effects on existing members, whether the operation is idempotent, or what happens on success/failure. For a write operation this is a notable gap.

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 compact clauses with no wasted words. The core action and target resource are front-loaded, and the key requirement (confirm=true) is included at the end, making it easy to scan.

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 straightforward mutation with strong schema coverage, the description plus schema is mostly sufficient for invocation. However, there is no output schema and the description does not explain return values, error behavior, or how to identify the project beyond what the schema references (group ID or project name). It is adequate but leaves gaps.

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%, so the schema already documents every parameter, including role enum and the confirm flag. The description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 ('Добавить участников') with a clear resource ('уже существующий проект (воркгруппу) Bitrix24'). It distinguishes itself from project creation and member-removal tools by explicitly targeting existing projects. The 'без похода в интерфейс' note adds operational context.

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 'в уже существующий проект' clearly sets the context: this tool is for adding members to an existing project, not for creating one. It does not explicitly name alternatives like bitrix_remove_project_members or bitrix_create_project, but the intent is unambiguous enough for an agent to route correctly.

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