jenkins_quiet_down

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

The description explains the behavioral impact (preventing new builds) and the safety guard (confirm: true). Annotations already indicate destructiveHint=true, and the description adds context on what that destructiveness entails. It could note reversibility but is otherwise sufficient.

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?

A single, concise sentence that is front-loaded with the core purpose and critical requirement. No wasted words.

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 tool with 3 parameters (one required), annotations, and no output schema, the description adequately covers the action, effect, and constraint. It could mention that it only affects new builds, but that is implied by 'no new builds will start'.

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?

Input schema has 100% coverage, so the baseline is 3. The description adds no additional parameter-level detail beyond highlighting the confirm requirement, which is already in the schema.

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 action ('Put Jenkins into quiet mode') and the effect ('no new builds will start until cancelled'), distinguishing it from sibling tools like jenkins_cancel_quiet_down.

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?

It specifies the required condition ('requires confirm: true'), which is a clear usage guideline. However, it does not explicitly contrast when to use this tool versus alternatives like jenkins_cancel_quiet_down, though the purpose implies its context.

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