jenkins_safe_restart

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

Annotations already provide destructiveHint: true. The description adds non-obvious behavior: it waits for running builds to finish and requires confirm: true. This goes beyond annotations by explaining the safety mechanism.

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?

One clear sentence that front-loads the purpose and key behavior. No unnecessary words or repetition.

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?

The description lacks mention of post-restart state, duration, or return value. While annotations cover destructiveness, the description could include warnings about Jenkins being temporarily unavailable or what happens if running builds are not drained in time.

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 100% and both parameters are well-defined with descriptions. The description reinforces the confirm parameter but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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 verb 'restart', the resource 'Jenkins', and the key behavior 'waits for running builds to finish'. It distinguishes this tool from siblings like jenkins_quiet_down which only prepares for shutdown, and jenkins_cancel_queue which cancels queued items.

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 when to use: when you need a safe restart that waits for ongoing builds. It mentions the confirmation requirement. However, it does not explicitly state when not to use or compare to alternatives like a force restart.

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