bitrix24_task_attach_file

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

With no annotations, description fully carries burden. Details two-step internal process (uploadfile then update), chat appearance without thumbnail, safety (preserves existing attachments), and the 'n<diskFileId>' encoding. No contradictions.

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?

Single paragraph, well-structured with purpose first, then guidance, then behavior, then safety, then implementation detail. Slightly long but all sentences add value; no redundancy.

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 4 params and no output schema, description covers purpose, usage, behavior, parameter nuances, safety, and internal steps. No gaps for effective invokation.

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 coverage is 100%. Description adds value beyond schema: explains default folder ID (732896) and its context (shared 'Блог' folder, writable for user 854), and that fileName defaults to basename. Provides override rationale for folderId.

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?

Clearly states the tool attaches a local file to a Bitrix24 task. Specifies file types and use cases (briefs, reports, signed-off specs). Explicitly distinguishes from sibling `bitrix24_task_post_image` for inline previews.

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?

Provides explicit guidance on when to use (delivering briefs, reports) and when not (images needing inline preview, alternatives given). Explains file appearance in chat (no preview) and safety behavior (append, not replace).

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