gitlab_list_pipelines

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

Declares 'Read-only and idempotent', which aligns with annotations (readOnlyHint, idempotentHint, destructiveHint). Adds details about output format (markdown table, PipelinesListOutput) and pagination, providing context beyond annotations.

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?

Efficient and well-structured: opens with purpose, then usage guidance, output description, and examples. Every sentence earns its place with no redundancy.

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 6 parameters (0 required), 100% schema coverage, and an output schema, the description covers usage, output shape, examples, and sibling differentiation completely. No gaps.

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 baseline is 3. The description adds value through concrete examples (e.g., 'status='failed', ref='master'') that illustrate parameter usage, going beyond schema field 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 states 'List recent pipelines of a project, newest first', providing a specific verb and resource. It further distinguishes itself from the sibling tool gitlab_get_pipeline by noting when not to use it.

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?

Explicitly states use cases: triage, release readiness checks, feeding pipeline IDs into follow-up calls. Also provides a clear when-not: 'Don't use when you have a specific pipeline ID — use gitlab_get_pipeline instead.'

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