get_artifact_pipeline

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds that the result includes a bounded set of compatible comparison candidates, which is useful behavioral context, but it does not explain how bounds are applied or what criteria determine compatibility.

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 very short and front-loaded, with no redundant phrasing. However, it is so terse that it omits usage guidance and parameter explanation, making it under-specified rather than optimally concise for the tool's context.

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?

The presence of an output schema and read-only annotations covers return-value structure and safety, but the core concept of 'bounded compatible comparison candidates' remains unexplained. The description also does not position the tool relative to nearby siblings like compare_artifact_pipelines or get_artifact, leaving room for incorrect tool selection.

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%, and the description never directly mentions pipeline_id or candidate_limit. 'One pipeline' loosely maps to pipeline_id and 'bounded' hints at candidate_limit, but the documentation does not clarify parameter semantics or the meaning of 'compatible comparison candidates.'

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 a specific verb ('Read') and resource ('one pipeline'), and adds that it also returns 'bounded compatible comparison candidates,' which distinguishes it from list or registration tools. However, it does not explicitly name an alternative or define what makes candidates 'compatible,' so differentiation is mostly implied.

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 use this tool versus alternatives such as list_artifact_pipelines, get_artifact, or compare_artifact_pipelines. The phrase 'Read one' implies a single-pipeline lookup, but no exclusions, prerequisites, or selection context are provided.

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