compare_artifact_pipelines

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

Annotations already convey that the operation is read-only, idempotent, and non-destructive. The description adds a useful behavioral guarantee: no native artifact content is returned. It also implies a compatibility and ordering constraint on the inputs, which is beyond the structural annotations.

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, front-loaded sentence with no filler. Every phrase contributes: the action, the scope, and a key output constraint. Structurally this is ideal for an agent to parse quickly.

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 strong annotations reduces the burden, and the simple two-parameter signature lowers complexity. However, the description leaves important context open: what 'compatible' means, what happens when stages are not compatible, and how this tool differs from other comparison tools in the same family. It is minimally viable but not rich enough for fully confident 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?

With 0% schema description coverage, the description needed to clarify baseline_pipeline_id and candidate_pipeline_id. It only obliquely implies they are 'comparable ordered stages'; the roles of 'baseline' versus 'candidate' are left to inference from the parameter names. This is insufficient compensation for the complete lack of schema-level parameter descriptions.

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 names a specific action and resource: compare artifacts pipeline stages. It also adds a distinct boundary ('without returning native artifact content'), which helps set expectations. However, it does not explicitly differentiate from sibling comparison tools such as compare_run_sets or compare_kernel_validation, so sibling differentiation is absent.

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 the tool is for comparing compatible, ordered stages of artifact pipelines, but it provides no explicit when-to-use guidance, prerequisites, or exclusions. It does not mention alternatives or explain when another comparison tool would be more appropriate.

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