List Power Platform pipelines

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly states 'Read-only' and names the underlying command ('pac pipeline list') and auth profile behavior, which is important contextual information for an agent deciding whether this command is safe and which profile to use.

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 compact and front-loaded with the core behavior, immediately followed by safety information and implementation detail. Every sentence adds value without unnecessary fluff.

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 the tool has six optional parameters and no output schema, the description covers the main behavioral modes, read-only safety, and the underlying pac command. It does not explain return structure, but for a list command this is reasonably inferable and the schema handles parameter details.

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 parameters are already fully documented. The description adds the semantic distinction between listing pipelines for an environment versus listing stages for a pipeline, but this is also largely reflected in the schema's 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 clearly identifies the resource (Power Platform pipelines), the action (list pipelines that can deploy from an environment), and the optional mode (list stages of one pipeline). It distinguishes from related tools like cs_deploy_pipeline without requiring the agent to infer the purpose.

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 provides clear context on when to use the tool: to see deployable pipelines from an environment or stages of a selected pipeline. It does not explicitly name alternatives or exclusions, but the dual-mode behavior is clearly stated.

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