bitrix24_task_comment_list

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

With no annotations provided, the description carries full burden. It discloses the fallback behavior and implies read-only operation. However, it does not mention pagination, sorting, or any potential side effects, which would further enhance transparency.

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 three sentences, front-loaded with the verb and resource, and every sentence provides value. No extraneous information.

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 no output schema, the description does not explain return format (e.g., fields like id, text, author). For a list tool, this is a gap. However, the tool name and sibling tools may imply structure, so not critically incomplete.

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?

The input schema covers both parameters with descriptions, achieving 100% coverage. The description adds no additional semantic meaning beyond what the schema provides (e.g., no explanation of how limit interacts with fallback). Baseline 3 is appropriate.

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 explicitly states 'Read task chat messages' and distinguishes from sibling write tools (add/update/delete) by specifying it is a read operation for task comments, with clarification that it reads from IM chat with fallback to legacy forum comments.

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 explains that modern Bitrix24 uses IM chat for task discussions and that this tool handles both modern and legacy formats via fallback. It gives clear context but does not explicitly mention when not to use it (e.g., versus other read tools like bitrix24_im_chat_messages).

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