Download Async

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

The description discloses two important behavioral traits: sessions are only created if the transfer actually starts, and local files are never overwritten. This is valuable because no annotations are provided. However, it does not explain the async semantics such as return values or how to retrieve results.

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 two short sentences, front-loaded with the core purpose. Every word contributes to the behavioral contract. It is appropriately concise without unnecessary filler.

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 three required parameters and no output schema, the description is insufficient for an agent to invoke this tool confidently. It omits parameter semantics, return values, and how to retrieve asynchronous results. The two disclosed behaviors are helpful but leave significant gaps in operational context.

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%, and the description provides no explanation of the three required parameters (machine, remotePath, localPath). The agent must rely solely on parameter names for meaning. The description fails to compensate for the lack of schema documentation.

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 'Async download', which clearly identifies the operation as a download variant. The 'Async' modifier distinguishes it from the sibling 'download' tool. However, it lacks detail about the resource being transferred beyond what the parameter names imply.

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?

No explicit guidance is given for when to use this tool versus 'download' or other siblings. The statements about session creation and file overwriting are behavioral constraints, not usage directions. No alternatives or prerequisites are mentioned.

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