gitlab_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. It mentions 'most recent' but does not disclose ordering (e.g., by date descending), pagination (beyond limit/max), or that it is a read-only operation. Partial transparency, but missing details.

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: one line for purpose, then two bullet-like lines for parameters. No unnecessary words, and the most important information (purpose) is front-loaded.

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 simple listing tool with two parameters, the description covers the basics well. It does not mention the output format, but an output schema exists (not shown). Could add context about ordering or response structure, but overall adequate.

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?

Both parameters are explained with examples and constraints: `project_path` is described as 'GitLab project path, e.g. 'group/project'', and `limit` has default 10 and max 100. This adds significant value beyond the empty schema 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 uses a specific verb ('List') and resource ('pipelines for a project'), clearly distinguishing it from siblings like `gitlab_get_pipeline` which fetches a single pipeline. It states it lists the 'most recent' pipelines, adding specificity.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for listing recent pipelines but does not compare with alternatives like `gitlab_get_pipeline` for detailed view or `gitlab_list_jobs` for pipeline jobs. Usage is clear but not differentiated.

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