get_workflow_run_artifacts

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: edition/license/permission gating and the fact that Community routes may return 404 or an empty list, which is exactly the failure mode an agent needs to anticipate.

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 short sentences, front-loaded with purpose then caveats. The trailing endpoint path partially restates the hierarchy already implied by the first sentence, but it is compact enough not to feel wasteful.

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?

There is no output schema, so the description should hint at what an artifact result looks like (names, links, sizes, merge behavior) and it does not. Safety and availability are covered, but the return shape — the main unknown an agent faces here — is left unstated.

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% for 3 required params, so the description must compensate. The included endpoint path (project/{project_id}/workflows/{workflow_id}/runs/{run_id}) does clarify the scoping hierarchy of the three IDs, which is useful, but it adds nothing about types, valid ranges, or how to obtain the IDs.

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?

Specific verb+resource: 'Get merged workflow run artifacts', which distinguishes it from siblings like get_workflow_run (run metadata) and get_task_output (task logs). The term 'merged' is left unexplained and slightly muddies what exactly is returned, but the resource is identifiable.

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?

It gives a conditional context ('availability depends on edition, license, and permissions; some Community routes return 404 or empty lists'), which is real usage guidance. However, it never says when to choose this over neighboring tools such as get_workflow_run or get_task_output, nor what preconditions to verify first.

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