Get Pipeline Job Output

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context: it returns a bounded window (max 1000 lines) from the end, and describes the output as 'untrusted' (likely meaning raw text without sanitization). This goes beyond annotations, though it does not cover all edge cases (e.g., behavior when job is still running).

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?

Two sentences, no filler. Every word adds value: 'bounded', 'untrusted', 'job trace window', 'Returns at most 1,000 lines from the end.' Highly efficient.

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 the complexity (4 parameters, no output schema, a context of pipeline jobs), the description is insufficient. It does not explain the required job_id, optional project_id, or how offset works. The agent may be unable to correctly invoke this tool without additional context.

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%, meaning the schema provides no descriptions for parameters. The description fails to mention any parameters (job_id, limit, offset, project_id). While 'bounded' hints at the limit parameter, it does not explain job_id or offset, leaving the agent without necessary guidance on how to fill the parameters.

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 tool retrieves a bounded, untrusted job trace window with a maximum of 1,000 lines from the end. The verb 'Get' and resource 'job trace window' are specific, and the behavior is distinct from sibling tools like gitlab_get_job_artifact_file or gitlab_get_pipeline_job.

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 usage for getting a limited tail of job output but does not explicitly state when to use this over alternatives. Sibling tools like gitlab_get_job_artifact_file or gitlab_download_job_artifacts are not mentioned, leaving the agent without guidance on choosing the correct tool for full logs or artifacts.

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