list_job_artifacts

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

With no annotations present, the description is the only disclosure of behavior; it states the operation returns a list of artifact file metadata, which is useful. However, it does not clarify whether the result includes directories, how recursion behaves, or whether pagination exists, and it does not describe the response structure beyond the four fields. The absence of an output schema increases the need for such detail, so this is only partially transparent.

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 that front-loads the primary action and resource, then appends the return fields. Every word adds information, with no filler or redundancy.

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?

The tool is a simple list operation, but with no output schema and no annotations, the description carries the full burden for both return shape and behavioral expectations. It conveys the returned fields but omits any guidance on required parameter combinations (e.g., job_id plus project_id) and does not note that this tool complements download_job_artifacts by enumerating what can be fetched. It is minimally complete but has clear gaps for an agent unfamiliar with the API.

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 input schema already documents all four parameters with descriptions, achieving 100% coverage, so the baseline is 3. The description adds no further parameter-level details, such as the relationship between job_id and project_id or how path and recursive interact. It does not need to repeat schema content, but it also does not enrich it.

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 ('List'), a specific resource ('artifact files in a job's artifacts archive'), and the returned fields (file names, paths, types, sizes). This clearly distinguishes it from sibling tools like download_job_artifacts or get_job_artifact_file, which retrieve content rather than enumerate it.

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 the tool is for inspecting the contents of an artifact archive before download, but it does not explicitly state when to prefer this over sibling tools such as download_job_artifacts or get_job_artifact_file. There is no direct mention of alternatives or exclusions, so usage context is inferred rather than spelled out.

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