Get Job Artifact File Local

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

The description adds some behavioral context beyond annotations: it saves to local directory, which is not read-only (consistent with readOnlyHint=false). However, it does not disclose important details like whether the local directory must exist, overwrite behavior, or error handling if the file is missing.

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, which is concise, but it is under-specified for a tool with 4 parameters and no schema descriptions. It fails to front-load critical details like required parameters or differentiation from sibling tools.

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 the complexity (4 parameters, no output schema, no parameter descriptions), the description is severely incomplete. It does not specify required parameters, explain local_path, or mention when project_id is needed. The context is insufficient for correct tool 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?

With 0% schema description coverage, the description must compensate. However, it provides no explanation of the parameters (job_id, artifact_path, local_path, project_id). It adds zero value beyond the raw schema types, leaving the agent with no clue about parameter roles or constraints.

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 action ('Save'), the resource ('one file from a job artifacts archive'), and the destination ('to a local directory'). It distinguishes from sibling 'gitlab_get_job_artifact_file' which likely returns file content rather than saving locally.

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 phrase 'Save one file' implies this tool is for extracting a single file, providing implicit usage context. However, it lacks explicit guidance on when to use this over alternatives like 'gitlab_download_job_artifacts_local' for entire archives.

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