Get pipeline

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful error behavior (`MissingParameterError`, `ParameterError`) and return shape (a wrapper with a Pipeline model), but it does not explain pagination, filtering, or why a single-pipeline fetch exposes parameters like `page`, `status`, and `variables`.

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 short and front-loaded with the core action. The Args/Returns/Raises structure is readable, though the generic `**kwargs` entry is not helpful and the argument section does not map cleanly to the actual schema.

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?

With 11 parameters, no output schema, and only 0% schema description coverage, the description is too thin to fully equip an agent. It clarifies the basic purpose and key missing-ID errors, but it leaves most parameter behavior and the relationship to sibling pipeline tools unexplained.

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% across 11 parameters, so the description must compensate, but it only mentions `project_id` and `pipeline_id` in the error section. It provides no semantics for `ref`, `data`, `page`, `status`, `variables`, or `api_parameters`, leaving most inputs undocumented.

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: 'Get information about a specific pipeline in a project.' This clearly identifies the operation as a single-pipeline lookup, though it does not explicitly contrast it with the sibling `gitlab_get_pipelines` or other pipeline-related tools.

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 does not explain when to use this tool versus alternatives such as `gitlab_get_pipelines`, `gitlab_get_pipeline_jobs`, or GraphQL pipeline operations. The error notes imply that `project_id` and `pipeline_id` are needed, but there is no explicit usage guidance or exclusion criteria.

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