list_workflow_run_artifacts

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic action and does not mention pagination, authentication, artifact expiration, or the nature of the returned data. The docs link offers details, but the description itself adds no behavioral insight beyond the tool name.

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 plus a docs link, front-loaded with the core action. Every word earns its place, and the additional documentation reference is unobtrusive.

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 simple read-only list operation, the description is minimally sufficient, but with no annotations and no output schema, it lacks context about what artifact information is returned, how pagination works, or any required permissions. The docs link partially compensates, but the description alone is not richly informative.

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 has descriptions for owner, repo, and run_id (60% coverage), but the tool description adds no parameter semantics. It does not clarify pagination parameters (page, per_page) or explain the relationship between run_id and artifacts, leaving gap in understanding for the undocumented parameters.

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 (list), the resource (artifacts), and the scope (workflow run), using a specific verb that distinguishes it from sibling tools like list_workflow_runs and list_workflow_run_jobs. There is no ambiguity about what the tool does.

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 when to use the tool (when you need artifacts from a workflow run) but provides no explicit guidance on when not to use it or which alternatives to prefer. It does not mention that this tool is specifically for artifacts, not runs or jobs, leaving selection up to inference.

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