List pipelines

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

With no annotations provided, the description carries full burden. It fails to disclose important behavior such as pagination (via continuationToken), default ordering, whether results are limited to a specific project (though project is optional), or what the response format is. It is a read-only operation by nature, but that is not stated.

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, brief sentence that front-loads the main purpose. It has no fluff, though it could have been structured to include more necessary detail without losing conciseness.

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 tool has 4 parameters, no output schema, and zero annotations. The description provides no information about parameters, pagination, return values, or error conditions. Given the complexity and lack of structured supplements, this description is seriously inadequate for an agent to call the tool correctly.

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 does not describe any of the 4 parameters. The schema itself only has type constraints, so an agent has no idea what 'orderBy' expects, how 'top' affects results, or what 'continuationToken' is for. The description completely fails to compensate for the missing parameter documentation.

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 states the verb ('List') and resource ('Azure Pipelines definitions in a project'). It is distinguishable from list_pipeline_runs, which lists runs rather than definitions, so the scope is clear.

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 explains what the tool lists but provides no guidance on when to use it versus alternatives like list_pipeline_runs or list_builds. There is no mention of prerequisites (e.g., project context) or typical use cases.

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