ado_pipeline_runs_list

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely useful behavioral context that annotations cannot convey: the Azure DevOps service cap of 10,000 and a 4 MiB response cap. It stops short of saying what happens when the cap is hit (truncation marker? error?).

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 tight sentences with the operation front-loaded and the limits second. No filler, no restatement of the tool name.

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?

For a tool with a nested target object, 0% schema coverage and no output schema, the description is too thin. An agent cannot tell what fields a run record contains, whether ordering is newest-first, or how the response cap manifests, all of which matter for correct invocation and interpretation.

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 'target' is a nested object with five undocumented sub-fields (profile, project, repository, repoPath, organization) whose interaction is non-obvious. The description mentions none of them and says nothing about pipelineId being a numeric identifier versus a name, so it fails to compensate for the coverage gap.

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 states a specific verb and resource ('List recent runs for a pipeline'), which clearly separates it from ado_pipeline_get and ado_pipeline_run_get (single entities) among the siblings. It does not explicitly name those siblings, so the differentiation is inferred rather than stated.

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?

There is no guidance on when to use this versus ado_pipeline_run_get or ado_pipeline_run, no mention of prerequisites or required scopes. The 'recent' framing implies a default ordering but never says how to retrieve older or more runs.

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