download_file

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the direction, source/destination, and protocol, but it does not mention local filesystem side effects such as overwriting local_path, FTP connectivity/auth requirements, or whether the printer is left unchanged.

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?

A single, focused sentence that front-loads the action and context without filler. Every word earns its place.

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?

The core call is understandable, but with no output schema or annotations, the description does not explain return behavior, how the optional printer parameter is resolved, or required prerequisites. These gaps require the agent to infer or discover details elsewhere.

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%, so the baseline is 3. The description adds only general framing ('SD card', 'local machine') rather than clarifying path syntax, the optional printer parameter, or how FTP endpoints are resolved.

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?

States the exact operation: downloading a file from a printer's SD card to the local machine via FTP. This clearly distinguishes it from sibling tools like upload_file, delete_file, and list_files by transfer direction and source/destination.

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 usage scenario is implied by the action: use it when you need to retrieve a file from the printer. However, there is no explicit guidance on when not to use it, no alternatives mentioned, and no prerequisites like FTP availability or prior use of list_files.

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