download

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

With no annotations, the description carries the full behavioral burden; it does disclose that folders are fetched recursively and in parallel and that the destination may be a file or an existing directory. It says nothing about permission requirements, whether existing local files are replaced (the overwrite default lives only in the schema), partial-failure behavior, or what is returned on success.

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 tight sentences with zero filler; the core action is front-loaded and the destination rule follows immediately. Nothing is repeated from the schema descriptions.

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 three-parameter, no-annotation, no-output-schema tool, the description covers the action and destination semantics but leaves out overwrite behavior and result reporting. Adequate for a straightforward transfer tool, but it does not fully compensate for the missing annotations.

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 baseline is 3, but the description adds real semantics beyond the schema for local_path: it clarifies that a trailing '/' or an existing folder means download-into, versus a plain path meaning target file. It does not explain how path interacts with local_path for recursive folder downloads.

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 a specific verb and resource ('Download a file or a whole folder ... to this machine') and adds scope details (recursive, parallel) that make the operation concrete. It does not name or differentiate from siblings like read_file, so an agent must infer which retrieval path to use.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as read_file or get_file_info. The agent must infer usage purely from the tool name and the folder-recursion detail.

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