gitlab_job_play

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

The annotation readOnlyHint=false marks this as mutating, and the description adds important context that dry_run defaults to true and only reads status, meaning the unsafe action requires opting out. However it omits permission requirements, side effects of actually playing a job, and error behavior for non-manual jobs.

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 short sentences, front-loaded with the action and immediately qualifying the default-safe mode. No waste.

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 mutating, no-output-schema tool, the description covers the critical safety default but leaves gaps: what playing a job returns, prerequisites on job state, and the required job_id semantics. Adequate but not complete.

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 33%: only project is documented. The description compensates partly by explaining dry_run's meaning and default, but job_id (the sole required parameter) is explained nowhere in schema or description.

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?

States a specific verb (play) and a specific resource (a manual job), which is distinguishable from sibling listing tools like gitlab_pipeline_jobs. It doesn't explicitly name sibling tools, but the 'manual job' scope is narrow enough that confusion is unlikely.

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?

Usage is implied: use it on manual jobs to trigger them, and dry_run reads the status instead. There is no explicit when/when-not guidance, no mention that the job must be in a manual state, and no comparison to alternatives such as gitlab_pipeline_jobs for inspecting jobs.

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