jenkins_restart

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does explain that safe mode waits for running builds while immediate restart may abort them, which is important destructive context. However, it doesn't mention whether restart requires admin/authentication permissions, the session constraints, or what happens to the current session connection during restart - gaps given restart is a disruptive action.

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 compact and front-loaded with the core purpose in the first sentence, followed by tight parameter explanations. Each sentence about parameters earns its place, though the Args section format with inline defaults is reasonable. Minor waste: the 'Args:' header and formatting could be trimmed, but otherwise 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?

For a destructive restart operation with no annotations and 0% schema coverage, the description covers the safe/immediate distinction well but omits important context: restart is disruptive to the server and all sessions, likely requires admin privileges, and the output schema (which exists) is not referenced. Enough for a competent agent to proceed safely, but gaps around permissions and session impact remain.

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 0%, so the description must fully document parameters. The description explains the 'safe' parameter's behavioral difference (wait vs immediate) and identifies 'session_name' for session selection. This adds meaningful semantic value beyond the bare schema, though session_name could use slightly more context on how sessions are established/used.

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 'Restart the Jenkins server' with a specific verb and resource. It distinguishes from sibling tools like quiet_down, which is a graceful shutdown, by focusing specifically on restarting the server rather than read/query operations.

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 explains the safe parameter behavior (safe vs immediate restart), which provides context on a key decision. However, it doesn't explicitly state when to prefer restart over quiet_down, disconnect, or other lifecycle tools, nor does it mention prerequisites like requiring an active session.

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