bx24_crm_activities

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but it only names operations like CRUD and complete without explaining consequences, reversibility, permissions, or side effects. The schema marks some actions as destructive, but the description text itself does not disclose these traits beyond what the structured data already says.

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 dense and front-loaded with the resource and operation families, but it is a single run-on paragraph that mixes keywords, method names, Russian/English phrases, and timeline subresources without clear structure. It is not bloated, but it lacks the organized readability that a tool with this many operations needs.

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?

Given the tool's high complexity (60+ action enum values, 12 parameters, nested objects, no output schema, no annotations), the description is incomplete. It does not explain which parameters are required for specific actions, what responses look like, how ownerId/ownerTypeId relate to binding semantics, or how destructive actions are confirmed. An agent would still need to infer much of this from the schema alone.

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 structured schema already documents all 12 parameters. The description adds no meaningful parameter semantics beyond the schema; the one contribution is mentioning fields like TYPE_ID and OWNER_TYPE_ID indirectly through broader method names, but that adds no extra value.

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 as Bitrix24 CRM activities (дела/звонки/встречи/письма) and enumerates the major operation families: CRUD, complete, todo, configurable, types, badges, and timeline. It is specific enough that an agent can tell this tool is about CRM activities rather than, say, deals or tasks. However, it does not explicitly distinguish itself from siblings like bx24_crm_calllists or bx24_telephony, which could overlap in the calls domain.

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 description implies usage for CRM activity management and lists method groups, but it does not state when to prefer this tool over alternatives or when not to use it. The action enum in the schema provides per-operation guidance, but the description itself gives no explicit when/when-not/alternative differentiation.

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