list_pipelines

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It merely says 'recent pipelines' without explaining ordering, pagination, the meaning of 'recent', or any authentication requirements. The minimal detail leaves the agent to guess about the tool's behavior.

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 concise and front-loaded. The first sentence states the purpose immediately, followed by a brief two-line argument list. Every sentence serves a purpose, and there is no extraneous text.

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?

While the tool is relatively simple and has an output schema, the description is thin. It does not specify the upper bound of 'recent', whether results are paginated, or if any filtering options exist. For a straightforward list tool, this is minimally viable but lacks context that would help an agent use it confidently.

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 must compensate. It clarifies that 'workspace' and 'repo' are slugs, providing meaning beyond the bare schema titles. However, it does not explain how these two parameters relate or whether both are required to identify a repository, leaving important gaps.

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 action ('List') and the resource ('recent pipelines (builds) for a repository'). It distinguishes itself from sibling tools like trigger_pipeline, stop_pipeline, and pipeline_steps, which perform different operations.

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 no usage guidance beyond the basic naming of the tool. It does not mention when to use this tool versus alternatives, nor does it specify any prerequisites or conditions. The only context is that it lists pipelines for a repository.

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