jenkins_copy_job

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

Annotations indicate the tool is not read-only (readOnlyHint=false), not idempotent, and not destructive, but the description adds no further behavioral context. It does not disclose potential side effects, such as whether a job with the new name already exists will be overwritten, or required permissions. The description merely restates the basic operation.

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, concise sentence that communicates the core purpose without excess words. It front-loads the essential action and resource, making it efficient for an agent to parse.

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 a straightforward operation and comprehensive schema coverage, the description provides a basic understanding. However, it lacks guidance on usage context, behavioral nuances, and differentiation from siblings, which is important given the large sibling group. It is minimally complete but not robust.

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?

All three parameters (fromName, newName, instance) are described in the input schema, achieving 100% schema coverage. The tool description adds no additional parameter information beyond what is already in the schema, so it meets the baseline expectation without enhancing understanding.

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 ('Copy/duplicate') and the resource ('a Jenkins job') with a specific outcome ('under a new name'). It effectively distinguishes from siblings like jenkins_rename_job (which alters the original job name) and jenkins_create_job (which creates from config).

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 provides no guidance on when to use this tool versus alternatives such as jenkins_rename_job or jenkins_create_job. It lacks context on prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage without explicit direction.

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