Download attachment

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

Annotations provide only false hints (not readOnly, not idempotent, not destructive). The description adds the download path and return value but lacks details on overwrite behavior, error handling, or side effects beyond saving the file.

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 sentence that front-loads the action and includes essential detail (download path). No unnecessary words.

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 reports the return value (local path). It covers the core functionality but omits edge cases like missing file or permission issues.

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% with detailed parameter descriptions, so the description does not need to add much. It does not elaborate on parameters, so 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?

Description uses specific verb 'скачивает' (downloads) and resource 'вложение' (attachment) with explicit destination folder. It clearly states what the tool does and is distinct from sibling tools, none of which perform downloads.

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 implicitly tells when to use (when you have a file_id) and there are no alternative download tools among siblings. However, it does not explicitly state prerequisites or contrast with other tools.

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