bx24_tasks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The top-level description mentions method families and RU/EN aliases but does not disclose side effects, destructive action warnings, permission requirements, rate limits, or response behavior. The schema's action enumerations label some actions as destructive, but that is structured data, not top-level description content.

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 compact, with the main scope front-loaded and a clear second sentence listing method families and language aliases. It avoids filler and communicates a large amount of coverage in two sentences. The dense method list is somewhat hard to scan but is still efficient.

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 tool with 22 parameters, 66 actions, and no output schema or annotations, the definition is only moderately complete. The input schema's action descriptions compensate significantly, but the top-level description provides no examples, no expected return shape, and no guidance for multi-step workflows. It is adequate for basic selection and invocation, but not comprehensive for such a large aggregate 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%, and each parameter already has a meaningful description, including the action enum with per-operation details. The top-level description adds no parameter-specific semantics, so the baseline score of 3 is appropriate. It neither helps nor harms parameter understanding beyond the schema.

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 tasks') and enumerates the major capability areas: lifecycle, checklists, comments, elapsed time, flows, stages, and planner. It distinguishes this tool from the CRM-focused siblings by stating the task domain explicitly. It lacks a single action-focused verb because it is an umbrella tool, but the scope is clear.

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 Bitrix24 task operations through the phrase 'Bitrix24 tasks' and the list of method families. It does not explicitly state when to use this tool instead of bx24_projects or other siblings, nor does it give when-not-to-use conditions. The usage context is inferred rather than stated.

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