gitlab_get_job

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says a job is fetched and repeats the HTTP method. It does not disclose what the response contains, whether additional scopes or project visibility are required, or how missing/invalid job IDs are handled.

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 a single, efficient sentence with no filler and the endpoint is front-loaded where it is most useful. It is appropriately brief for such a small tool, though the brevity borders on under-specification in other dimensions.

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 read tool with no output schema and no annotations, the description should at least indicate what data is returned and how to obtain a valid job ID. It does neither, and it omits the natural connection to sibling tools like gitlab_get_pipeline_jobs, leaving the agent without enough context to call it reliably.

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 only 50%, and the description does not compensate: jobId is left entirely undocumented, and projectId's meaning must be gathered from the schema. The endpoint template hints that projectId maps to ':id' and jobId to ':job_id', but this is minimal and indirect.

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 the specific verb 'Gets a job' and names a concrete resource, backed by the exact GitLab REST endpoint. It is clear that this tool retrieves a single CI job by ID, though it does not explicitly contrast itself with the sibling gitlab_get_pipeline_jobs.

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?

There is no guidance about when to use this tool versus related alternatives like gitlab_get_pipeline_jobs or gitlab_get_pipeline. The description merely states what the endpoint does, leaving the agent to infer that it should be used when a specific job ID is already known.

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