Get job artifact

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context by explaining that a single image path returns a viewable image, hinting at response format. It does not discuss error handling or auth, but with minimal annotations this extra context earns a solid score.

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?

Two sentences, 22 words, with the primary action front-loaded. Every word earns its place; no fluff or repetition.

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 read-only artifact download, the description is nearly complete with good annotations and schema coverage. It briefly mentions image return behavior, but could be more explicit about non-image artifact returns (e.g., archive download). Overall, sufficient for an agent to invoke correctly.

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?

The schema already describes project_id and artifact_path well, providing 67% parameter coverage. The description does not add new parameter-specific details beyond the schema, though its artifact path examples (screenshots) implicitly reinforce what artifact_path accepts. Baseline 3 is appropriate.

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 'Downloads a CI artifact' with a direct verb and resource, clearly distinguishing it from sibling tools like gitlab_get_job_log or gitlab_job_action. The addition of the image path example (Playwright/Cypress screenshot, coverage badge) specifies a common use case, further clarifying scope.

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: to download CI artifacts, especially image-like artifacts. It does not explicitly mention alternatives or when not to use it, but the context is clear enough for an agent to differentiate from job log retrieval or job control.

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