download_pipeline_artifact

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that only textual content is returned, which hints binary artifacts are not handled, but it says nothing about permissions needed, file-size or truncation limits, or error behavior when the runId/artifactPath does not resolve.

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?

A single front-loaded sentence that states the action, the source location, and the return type with zero filler. Nothing is redundant or buried.

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 four-parameter read tool with a fully documented schema and no output schema, the description covers what the agent gets back (textual content) and where it comes from. The remaining gaps — binary handling and large-file truncation — are minor but nonexistent in both schema and description.

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% — every parameter, including the optional pipelineId guard and the artifactPath format, is documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb (Download) and a precise resource (a file from a pipeline run artifact), and adds that the result is the textual content. Combined with the name, an agent can distinguish it from repository-file tools like get_file_content and log tools like get_pipeline_log, though the description itself does not name those siblings.

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?

Usage is only implied: 'pipeline run artifact' scopes it away from repo files and logs, but there is no explicit when-to-use statement, no mention of the alternative retrieval tools, and no preconditions. Minimum-viable scoping without routing guidance.

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