ado_pipelines_list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds genuine behavioral context beyond them — that results are paged and how to continue — but says nothing about ordering, page size defaults, or the shape of returned items.

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 short sentences, both earning their place, with the paging instruction front-loaded rather than buried. Nothing is wasted, though the brevity leaves the nested target parameter unaddressed.

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?

A nested-object, 0%-coverage schema with no output schema needs more than two sentences. The agent is never told what a target must contain to resolve a pipeline scope, nor what a returned pipeline record looks like, which is significant for a list tool with no output schema.

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%, so the description carries the full burden, yet it only explains continuationToken. The required `target` object (with profile, project, repository, repoPath, organization) and the `top` page-size parameter with its 1-100 bounds are entirely undocumented anywhere.

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 ("List a page of pipelines"), which cleanly separates it from ado_pipeline_get and ado_pipeline_runs_list in the sibling set. It stops short of stating the scope (which project/repository the pipelines belong to), so an agent must open the schema to learn that.

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 only guidance is a pagination mechanic (pass continuationToken back), not when to choose this over ado_pipeline_get or ado_pipeline_runs_list. No prerequisites, no mention of required target scoping or what to do when the list is empty.

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