Download Job Artifacts

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint. The description adds that output is base64 content, but does not disclose other behavioral traits like permission requirements or error handling. It meets the minimum but adds limited extra value.

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 a single sentence of 10 words, highly concise and front-loaded. No wasted words, but it could be slightly longer to add useful context without becoming verbose.

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 tool with 2 parameters, 0% schema coverage, and no output schema, the description is too sparse. It does not explain the return value format (base64 encoding details), prerequisites (job must have artifacts), or link to related tools. The agent lacks critical context for correct usage.

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%, so the description must clarify parameter meanings. It mentions 'job_id' implicitly but offers no additional information about parameter purpose, format, or how to find them. The name 'project_id' is not explained. This is a significant gap.

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 clearly states the verb (Download), resource (full job artifacts archive), and output format (base64 content). It distinguishes from siblings like gitlab_get_job_artifact_file and gitlab_download_job_artifacts_local by indicating 'full' archive vs individual files or local storage.

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 guidance is provided on when to use this tool versus alternatives such as gitlab_get_job_artifact_file (for individual files) or gitlab_download_job_artifacts_local (for local saving). The description does not mention any prerequisites or context.

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