jenkins_delete_job

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

Despite no annotations, the description explicitly discloses the destructive nature with 'This action cannot be undone. All build history will be lost.' This is a strong behavioral disclosure covering the most critical aspect. It doesn't address permissions/auth requirements, but the 'session_name' parameter hints at session-based auth context. Given no annotations carry any burden, this is solid disclosure of the key irreversible consequence.

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?

Compact and front-loaded with the purpose and the critical warning. The warning is well-placed right after the purpose line. The Args section is minimal and helpful. Slight redundancy between 'cannot be undone' and 'All build history will be lost' but both add distinct value.

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?

This is a critical destructive action with no annotations, so disclosure of irreversibility is essential and provided. The output schema presence means return-value description is not needed. The main gap is lack of session/auth prerequisites, but for a simple delete operation the description covers the essential risk information adequately.

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 0%, so the description carries the full burden. It does explain job_name format ('use folder/job-name for jobs in folders') which adds real value beyond the bare schema. However, session_name is not explained at all beyond 'Jenkins session to use' - the description mentions it in Args but provides minimal semantics about its meaning or default behavior.

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 it 'Delete a Jenkins job permanently' - specific verb (delete) + resource (Jenkins job) + permanence qualifier. Distinguishes from siblings like jenkins_delete_build, jenkins_delete_view, and jenkins_delete_credential by targeting 'job' specifically.

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 warns this is permanent and irreversible, giving clear context that this is a destructive operation. However, it doesn't explicitly contrast with alternatives (e.g., disable_job as a non-destructive option) or state when to prefer this over siblings.

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