Run pipeline

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a potentially mutating action ('Queue') but does not state side effects, the confirmation requirement, authentication needs, or what preview does differently from a real queue.

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 word contributes to stating the action and the main optional inputs.

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?

Given 8 parameters, nested objects, no output schema, and no annotations, this description is too sparse. It omits the confirmation gate, preview semantics, how variables/templateParameters are structured, and what the caller can expect in return.

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 only 13%, so the description must compensate, but it only loosely references 'branch, variables, parameters, and skipped stages' without mapping to exact parameter names or explaining semantics. Critical parameters like pipelineId, confirm, previewRun, and project are not addressed.

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 uses a specific verb-resource pair ('Queue or preview an Azure Pipeline run') and names the key configurable dimensions (branch, variables, parameters, skipped stages). This clearly differentiates it from siblings like list_pipeline_runs, get_pipeline_run, and rerun_pipeline.

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 its use case: triggering or previewing a pipeline run. However, it gives no explicit guidance on when to choose this over alternatives, nor does it explain the queue-vs-preview decision or mention exclusions.

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