bitrix_create_task

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states this is a write operation requiring confirm=true, and explains that Bitrix24 rejects the task without responsibleId. It does not cover return values or error cases, but the core behavioral requirements are disclosed.

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?

Three short sentences, front-loaded with the main purpose, followed by critical constraints (responsibleId, confirm). No fluff or redundant elaboration.

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 7-param create tool with no output schema and no annotations, the description covers the essential invocation contract: what is created, project vs standalone, required responsibleId, and confirm flag. Optional params are left to the schema, which is reasonable given their descriptions. Missing permission/error context is a 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 10000%, so the schema already documents all seven parametes. The description adds emphasis on responsibleId and confirm requirements and clarifies projectId semantics, but does not materially extend beyond the schema's own descriptions.

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 uses a specific verb and resource: 'Создать новую задачу' (create a new task), and distinguishes between project-bound and standalone tasks. This clearly separates it from siblings like bitrix_update_task, bitrix_start_task, and bitrix_complete_task.

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?

It gives clear context for when to use the tool (creating a new task) and how to choose between a project task and a standalone task via projectIdparameter presence. It does not explicitly name alternative sibling tools, but the context is clear enough.

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