jenkins_delete_job

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

Annotations already mark the tool as destructive (destructiveHint=true), so the description adds the specific permission flags required, which is useful operational context. It does not disclose that deletion is permanent or that the job parameter can accept an array for batch deletion, but the core safety trait is covered by annotations.

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 two short sentences, front-loading the primary action and then adding a compact permission note. Every word earns its place with no redundant or filler text.

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 single-parameter destructive operation, the description covers the action and required permissions, and the existing annotations plus output schema fill in safety and return-value details. It could mention batch deletion or irreversibility, but the tool is simple enough that the description is largely adequate.

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 provides no description for the 'job' parameter (0% coverage) and the description does not explain it either. The parameter name and the action give some clue that it is a job name, but the description fails to mention the accepted array form or any formatting requirements.

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 defines the action precisely as 'Delete a job' with a specific verb and resource, and this is clearly distinct from sibling tools like jenkins_create_job, jenkins_copy_job, and jenkins_disable_job. The permission note does not obscure the core 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?

There is no explicit guidance about when to use this tool over alternatives or when not to use it. The intended use is implied by the verb 'Delete', and the permission requirement ('Requires write, job-config, and delete flags') provides a precondition but no routing to or from sibling tools.

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