parse_artifact

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that the tool performs a network download from GitHub and which four test-report formats are accepted, which is real behavioral context. However, it is silent on authentication requirements, whether the download is cached, and how malformed or unsupported artifacts are handled.

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 tightly written sentences with zero filler; the core action is front-loaded and the format enumeration is compressed into a single compact clause.

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?

With no annotations and no output schema, the description should shoulder more of the burden — particularly what the parsed result looks like (a structure? a summary? failures only?) and how it relates to get_failures/get_test_detail. The format list is helpful, but the return contract is left entirely to inference.

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 100%, so repo, runId, and artifactName are already documented in the schema, making the baseline 3 appropriate. The description adds only the format-detection behavior, not additional parameter semantics such as whether artifactName is case-sensitive or a glob.

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 two specific verbs (download, parse) against a concrete resource (GitHub Actions artifact) and names the output domain (test results). It implicitly differentiates from siblings like list_artifacts and parse_log, though it never names them explicitly.

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 guidance on when to reach for this tool versus list_artifacts, parse_log, or get_test_detail, nor any stated prerequisite such as needing a prior list call to obtain artifactName. The supported-format list hints at applicability but does not constitute usage routing.

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