download_file

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

With no annotations, the description must convey behavior. It explains the download operation and file path, and implies asynchronicity by referencing list_downloads. However, it omits details such as error handling, permissions, or confirmation that the file is saved on the teamserver.

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 relatively concise, front-loading the purpose, and includes a usage section with arguments and example. However, the phrase 'Task the agent to download' could be slightly tightened, and the structure is clear with no wasted sentences.

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 the tool's complexity (2 required params, output schema exists), the description covers the download action and file path but omits prerequisites like agent connectivity and file existence. It references related tools but lacks full completeness for a 2-param mutation tool.

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. It explains remote_path with example and full path requirement, but fails to describe agent_id, which is also required. Only one of two parameters is semantically enhanced.

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 clearly states 'download a file to the teamserver', specifying the verb, resource, and destination. It distinguishes from siblings like get_downloaded_file or list_downloads, and includes a concrete example.

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 provides usage context by showing the command format and example. It also references sibling tools list_downloads and get_downloaded_file for post-download steps, though it does not explicitly state when not to use this tool.

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