Get job artifact archive

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond annotations: it is a complete archive download, returned as bounded base64 data. It does not detail truncation or error behavior, but the annotation coverage lowers the burden.

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 one short, front-loaded sentence with no filler or repetition. Every word adds meaning.

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 simple download tool with an output schema and strong annotations, the description covers the core purpose and output format. However, it leaves gaps around max_bytes behavior and does not differentiate from get_job_artifact_file, so it is not fully complete 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 only 33%, so the description should compensate for undocumented parameters. It does not explain max_bytes or job_id semantics beyond the obvious. 'Bounded base64 data' hints at size limits but does not connect to the max_bytes parameter or its behavior.

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') and names the exact resource ('GitLab job's complete artifact ZIP archive') plus output format ('bounded base64 data'). It distinguishes this from sibling get_job_artifact_file by emphasizing the complete archive vs. a single artifact file.

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 it by saying 'complete artifact ZIP archive,' but it never explicitly contrasts with alternatives like get_job_artifact_file or states when this tool should not be used. There is no exclusion or alternate-tool guidance.

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