jenkins_delete_job

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

Annotation already provides destructiveHint=true, but description adds explicit context: 'permanently delete' and 'WARNING: cannot be undone'. This clarifies the behavior beyond the annotation, though it does not disclose authorization needs or error scenarios.

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 a single, front-loaded sentence with no redundant words. Every part—action, resource, and warning—earns its place.

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 no output schema, the description omits details on return behavior or error handling. While the core action is clear, a delete tool would benefit from indicating success indicators or side effects.

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 description coverage is 100% for both parameters (jobName and instance). The description does not add any new information about parameters beyond what the schema provides, meeting the baseline expectation.

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?

Description clearly states 'Permanently delete a job' with a specific verb (delete) and resource (job). It distinguishes from sibling tools like jenkins_disable_job and jenkins_create_job by emphasizing permanence and destruction.

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 includes a warning about irreversibility but does not specify when to use this tool versus alternatives like jenkins_disable_job or jenkins_rename_job. No explicit when-not-to-use guidance is provided.

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