bx24_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'user CRUD' which implies create/update/delete, but it does not disclose destructive side effects, confirmation requirements, permission needs, or the persistence impact of actions. This is under-disclosed for a tool that can add, update, and delete users and user fields.

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 first portion is reasonably compact and front-loads the resource and actions. However, the RU/EN synonym list adds significant token length and mostly duplicates meanings already present in the action names, making the description noisier than necessary. It is not as tight as it could be.

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 high-complexity tool with 12 parameters, 13 actions, nested objects, no output schema, and no annotations. A short tagline is not enough for an agent to understand return shapes, pagination, destructive confirmations, or permission prerecordites. The schema fills in parameter details, but behavioral and usage context remains incomplete.

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 every parameter already has a descriptive comment in the input schema. The description itself adds no parameter-level meaning, but it doesn't need to compensate because the schema covers the details. Baseline 3 is appropriate 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 clearly identifies the resource (Bitrix24 portal users) and enumerates the core operations: current, get, search, list by department, user fields, and CRUD. This gives an agent a solid idea of what the tool covers and how it relates to the 'users' domain. It loses a point because it reads as a capability list rather than a single scoped verb, and it doesn't explicitly distinguish itself from sibling tools like bx24_departments or bx24_hr.

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?

There is no guidance on when to use this tool versus alternatives. The RU/EN synonym list hints that this tool can answer 'who am i' or 'find user', but it does not state criteria for choosing this tool over others, or when not to use it. The action enum in the schema provides operational detail, but the description itself offers no decision support.

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