Get pipeline data

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

readOnlyHint=true already declares this a safe read. The description adds that it returns the full definition and can pin to a specific revision, which is useful, but it says nothing about the git-backed vs versioned YAML distinction or the account-scoping behavior that the schema only hints at. Adequate but not rich.

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 tight sentences with the primary selector front-loaded and the optional revision path second. No filler, though the second sentence compresses several distinct selector types into one 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?

An output schema exists so return values need not be explained, and the schema fully documents the parameters. The description is complete for the core flow, with only minor gaps around the yaml_path/repository pair and account-override semantics, which the schema already covers.

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 the schema already documents all eight selectors. The description repeats the primary ones (pipeline_id, alias, version, branch, commit) without adding format or mutual-exclusion rules, and omits yaml_path/repository pairing entirely. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Fetch the full pipeline definition') and clarifies that selection is by pipeline_id or alias, with optional revision selectors. It partially distinguishes itself from siblings like get_pipeline by emphasizing the full definition plus revision loading, though it never names those siblings 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?

It explains how to select a pipeline and that version/branch/commit load a specific revision, which implies usage. But it gives no guidance on when to prefer this over get_pipeline, list_pipelines, or pipeline_context, and no prerequisites or exclusions are stated.

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