l2kc_download_artifacts

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It notes that mock data are test fixtures, which is a useful caveat, but it does not disclose whether downloads overwrite files in `dest_dir`, what permissions are required, how conflicts are handled, or any rate limits.

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 brief and front-loads the action, but the two sentences are cryptic rather than efficiently informative. The fixture warning is useful, yet the overall structure leaves key operational details absent rather than concisely explained.

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 a required `job_id`, an optional destination directory, and no annotations, the description is incomplete. The output schema may cover return values, but the description does not explain how to invoke the tool correctly, what `job_id` identifies, or how `dest_dir` affects behavior.

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 compensate, but it does not meaningfully explain either parameter. `job_id` is required yet entirely undocumented, and `dest_dir` is not mentioned at all; the description's reference to ``artifact_root`` is not a parameter name and does not clarify the schema.

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 a specific verb and resource: 'Download artifacts under ``artifact_root``.' This is clear enough for an agent to understand the basic action, but it does not distinguish this tool from its obvious sibling `gpu_download_artifacts`, leaving ambiguity when both are available.

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?

There is no explicit guidance on when to use this tool versus `gpu_download_artifacts` or other siblings, nor any prerequisites such as authentication or job completion state. The only usage-adjacent statement is that mock data are test fixtures, which does not help select between alternatives.

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