bitrix_get_task_checklist

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Получить' indicates a read operation, and the acceptance-criteria framing adds useful semantic context. Still, the description does not mention error behavior, permissions, what happens when the checklist is absent, or output shape.

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 a single, focused sentence with no filler. It states the action and the resource efficiently, and the acceptance-criteria qualifier earns its place by clarifying the intended interpretation of the returned checklist.

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 simple one-parameter read operation, the description covers the core purpose and context. However, since there is no output schema, the description could have briefly noted the expected return structure or edge cases, such as an empty or missing checklist. This leaves a noticeable but minor gap.

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 the single taskId parameter is already described as 'ID задачи.' The tool description adds no additional parameter detail beyond confirming the checklist belongs to a Bitrix24 task, so the schema remains the primary source of parameter meaning.

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 names a specific verb ('Получить') and resource ('чек-лист задачи Bitrix24'), adding the semantic framing 'как критерии приёмки' to clarify the checklist's role. It is distinguishable from the sibling bitrix_get_task because it targets the checklist specifically, though it does not explicitly contrast itself with that sibling.

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 'как критерии приёмки' implies the tool should be used when acceptance criteria for a task are needed, providing some usage context. However, there is no explicit guidance about when to use this tool versus alternatives like bitrix_get_task, and no stated exclusions or conditions.

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