download_job_artifacts

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

No annotations are provided, so the description carries the disclosure burden. It clearly states the operation, the object being downloaded, the destination, and the return value. However, it does not mention behaviors like overwriting existing files, creating directories, or failure behavior when the job has no artifacts.

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 sentence conveys the action, resource, destination, and return value with no filler. The most important scoping detail ('entire artifact archive') is front-loaded.

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 straightforward download tool with fully documented parameters, the description is largely complete: it explains the scope of the download and the return value. Minor gaps remain around alternative-tool routing and edge-case behavior, but nothing essential is missing for basic invocation.

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 the schema already documents all three parameters. The description adds that the download is a zip archive and that local_path is the destination, but it does not meaningfully extend parameter semantics beyond the schema.

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 uses a specific verb ('Download'), a concrete resource ('entire artifact archive (zip) for a job'), and a clear destination ('local path'), while also stating the return value. The phrase 'entire artifact archive' distinguishes it from sibling tools like get_job_artifact_file or list_job_artifacts.

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 implies when to use the tool—when you need the whole job artifact archive as a zip—but it does not explicitly compare it to alternatives such as get_job_artifact_file or list_job_artifacts. There is no when-not-to-use guidance.

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