Download Job Artifacts Local

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

The description adds little beyond annotations: it states 'Download' implying file creation but does not disclose overwrite behavior, required permissions, or side effects. With readOnlyHint=false and destructiveHint=false, more context is needed to avoid surprises.

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 sentence and concise, but it sacrifices necessary detail. It could be expanded without losing conciseness to include critical usage hints.

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 lack of output schema and the presence of sibling tools, the description is incomplete. It does not mention how the archive is saved (filename, directory resolution), return value, or error conditions. The agent lacks key information for successful 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 coverage is 0%, so the description should clarify parameter meanings. It only mentions 'full job artifacts archive' and 'local directory' but fails to explain how local_path (optional) is used or what project_id is for. This leaves the agent guessing about required inputs.

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 (Download), the resource (full job artifacts archive), and the destination (local directory). However, it does not distinguish from sibling tools like gitlab_download_job_artifacts or gitlab_get_job_artifact_file_local, which could be confused.

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_local (for single file) or gitlab_download_job_artifacts. The description lacks any context or exclusion criteria.

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