bx24_workflows

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

No annotations are present, so the description carries the full behavioral burden. It only lists method groups and keywords; it does not disclose that many operations mutate state, which ones are destructive, what side effects starting or killing workflows has, or any authorization requirements. The schema's action labels mark some operations destructive, but the main description itself is nearly silent on behavior.

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 opening sentence is compact and front-loads the domain and method groups. However, the RU/EN keyword list adds noise, contains a malformed token ('杀ить'), and provides limited value to an AI agent deciding how to invoke the tool.

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?

The schema is rich and documents all 25 actions with descriptions, which compensates for the sparse top-level description. Still, there is no output schema and no main-description guidance on return shapes, workflows vs tasks boundaries, or common usage patterns, so the definition is adequate but has clear gaps for such a complex multi-action tool.

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 baseline is 3. The top-level description adds no parameter-level meaning, but the action enum descriptions inside the schema provide detailed operation-specific parameter hints. The description does not need to duplicate what the schema already documents.

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 Bitrix24 business process domain and enumerates the main subresources (templates, instances, tasks, robots, activities) and REST method groups. It is broad rather than a single verb+resource, but that fits a multi-action tool and distinguishes it from the CRM/tasks/disk siblings.

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 scope implies when to use the tool: operations on Bitrix24 business processes and robots. However, it gives no explicit guidance about when not to use it, how it relates to bx24_tasks (regular tasks vs workflow tasks), or when an alternative sibling would be more appropriate.

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