Download Files

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

No annotations are provided, so the description carries the whole behavioral burden, yet it discloses nothing beyond the bare purpose. It does not say whether the operation is read-only, whether results are paginated, whether NAS credentials (host/port/scheme/profile) are required, or what happens for a missing or unauthorized task.

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 short sentence with no redundancy and the purpose stated up front. Its brevity is efficient, though it borders on under-specification for a five-parameter tool.

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 five parameters, an optional NAS connection group, and no annotations, the description is far too thin; it never explains how the host/port/scheme/profile parameters interact or when they are needed. The presence of an output schema excuses it from explaining return values, but the invocation-side gaps remain significant.

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 100%, so all five parameters including task_id and the NAS connection parameters are documented in the schema itself. The description adds no extra meaning about task_id format or when the optional connection parameters must be supplied, so the baseline applies.

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 concrete verb+resource: listing the files belonging to a download task. However, the tool name and title ('download_files' / 'Download Files') imply actually fetching files, which conflicts with a read-listing action, creating ambiguity about what the tool really does. It also does not distinguish the tool from close siblings such as download_info or download_list.

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 guidance on when to call this rather than download_info, download_list, or download_stats, and no mention of when a task_id is valid or what state the task must be in. The agent must infer usage entirely from the tool name.

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