gitlab_get_pipeline_jobs

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It only states a GET endpoint, which hints at read-only behavior, but it does not mention pagination, whether all jobs are returned, or what the response contains; this is thin coverage for a tool with no annotation support.

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 extremely compact: a one-phrase resource statement followed by the exact API endpoint. Every word earns its place, and the key information is front-loaded before the parenthetical endpoint.

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 two-parameter listing operation, the description is minimally sufficient: it identifies the inputs conceptually and the expected collection of jobs. However, with no output schema and no annotations, the lack of any mention of response format, pagination, or permissions leaves notable gaps in what an agent needs for robust use.

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 coverage is 50%, with projectId already described. The endpoint string adds a little value by clarifying that pipelineId maps to the ':pipeline_id' path segment, but the description does not meaningfully expand on the schema or add context for how the parameters relate, such as requiring an existing pipeline.

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 specifies the resource ('jobs of a pipeline') and even gives the exact HTTP verb and path ('GET /pipelines/:pipeline_id/jobs'), so the tool's action and target are unambiguous. It also differentiates from siblings like gitlab_get_pipeline and gitlab_get_job by clearly focusing on the plural jobs collection.

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 implies the correct use case: when you need the jobs belonging to a particular pipeline. However, it never explicitly states when not to use it or mentions alternatives such as gitlab_get_job for a single job, leaving the routing decision to inference from sibling names.

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