bitrix_lists_get_letter_file

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. It reveals that the tool returns file content base64-encoded and downloads a single attachment. It doesn't address error cases, size limits, or read-only status, but the return format is a worthwhile behavioral detail.

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?

Two concise sentences with no filler: the first states the action and resource, the second the return format. Everything is front-loaded and necessary.

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?

With no output schema and no annotations, the description is the only source of context. It defines the ID source and the base64 return encoding, but leaves the required direction parameter ambiguous, so an agent cannot reliably know what to pass for 'incoming' vs 'outgoing'. This is a significant gap for correct invocation.

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 0%, so the description must compensate for both parameters. It explains attachedObjectId by pointing to bitrix_lists_search_letters, but the required direction parameter (incoming/outgoing) is not explained at all; the schema enum only lists possible values without conveying their 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 states a specific verb ('Скачать' / download), a specific resource (content of one email attachment from the 'Lists' registry), and the lookup key (attachedObjectId obtained from bitrix_lists_search_letters). This clearly distinguishes the operation from its sibling bitrix_lists_search_letters.

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 names the upstream tool that produces the required attachedObjectId, making the intended workflow 'search first, then download' explicit. It doesn't state explicit when-not-to-use cases, but the sequencing is clear enough for an agent.

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