get_pipeline_runs

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

No annotations are provided, so the description must fully convey behavior. It only states the basic action (get) without indicating whether it is read-only, idempotent, or has any side effects. The 'recent' qualifier is vague and lacks detail on criteria like ordering or time window.

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 concise sentence with no extraneous content. It is efficiently structured but could benefit from slightly more detail without becoming verbose.

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 no output schema, so the description should explain what the return value contains (e.g., list of run objects, fields). It does not, and it also fails to clarify the meaning of 'recent' (e.g., most recent by run ID? date?). This leaves significant gaps for the agent.

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?

The input schema has 100% coverage with descriptions for all parameters (top, project, pipelineId). The tool description adds no additional semantic context beyond these schema descriptions. Baseline score of 3 is appropriate since the schema already fully documents parameters.

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 that the tool retrieves recent runs of a pipeline, which distinguishes it from siblings like 'get_pipelines' (list pipelines) or 'get_work_item'. However, it does not clarify what 'recent' means in terms of time or ordering, leaving some ambiguity.

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?

Usage is implied: use when you need runs of a specific pipeline. No explicit when-to-use or when-not-to-use guidance is provided, nor are alternatives mentioned. The sibling list suggests other retrieval tools, but no contrasts are drawn.

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