Retry Pipeline Job

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate it is a mutation but not destructive. The description does not elaborate on behavioral traits: it does not specify that retry only applies to failed jobs, what happens if the job is not failed, or any side effects like triggering a new pipeline. Minimal disclosure beyond annotations.

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 concise (one sentence). While it is front-loaded, it sacrifices crucial information about parameters and usage. It is not overly verbose but is under-specified.

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 tool has 2 parameters and no output schema, the description should explain prerequisites (failed job) and parameter roles. It fails to provide enough context for an agent to use the tool correctly.

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%, and the description does not explain the meaning of parameters (job_id, project_id). Without context, an AI agent cannot understand what values to provide or the role of each parameter.

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 'Retry one failed job.' clearly states the action (retry) and the resource (one failed job). It distinguishes from sibling tools like gitlab_retry_pipeline (retries entire pipeline) and gitlab_play_pipeline_job (plays a job, not necessarily a retry).

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 guidance is provided on when to use this tool versus alternatives. There is no mention that the job must be in a failed state, nor any prerequisites like permissions. The description lacks context for appropriate usage.

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