jenkins_stop_build

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

With no annotations, the description carries the full burden of behavioral disclosure. It correctly identifies the tool as a write operation ('stop') and mentions an environment variable requirement. However, it does not describe side effects, error conditions (e.g., if the build is not running), or what the response looks like.

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 consists of two short sentences, each adding essential information. There is no unnecessary detail, and the key action is stated upfront. It is a model of conciseness.

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's simplicity, the description is minimally adequate. It covers the core function and a key requirement. However, it omits any reference to the output schema (which exists) and could benefit from a brief note about what happens on success/failure. Still, it meets basic needs.

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?

The input schema has 0% description coverage, meaning no parameter descriptions are provided in the schema. The tool description itself adds no explanation of the 'job' and 'build' parameters (e.g., format, constraints). This forces the agent to infer from names alone, which is insufficient.

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 'Stop a running build' uses a specific verb and resource, clearly indicating the tool's action. It distinguishes itself from sibling tools like 'jenkins_trigger_build' (starting) and 'jenkins_cancel_queue_item' (cancelling queued items), leaving no ambiguity about its purpose.

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 mentions a prerequisite ('Requires JENKINS_MCP_ENABLE_WRITES=1'), providing some usage context. However, it does not explicitly state when to use this tool versus alternatives (e.g., cancelling a queued build vs. stopping a running one), nor does it give exclusion criteria.

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