jenkins_copy_job

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

With no annotations, the description carries the full burden. It only states that copying requires certain flags, without disclosing side effects (e.g., whether it overwrites existing jobs), authorization details, or error scenarios. The existence of an output schema is not leveraged to explain return behavior.

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 very concise: two sentences with no fluff. Every sentence adds information (action, resource, requirement). However, it could be slightly more detailed without losing conciseness.

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 the existence of an output schema, the description need not explain returns, but it should cover operational behaviors like overwrite handling, job existence checks, and folder limitations (despite specifying 'top-level'). The description omits these, making it incomplete for a mutation tool.

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 has 2 parameters with 0% coverage, and the description adds no explanations for `from_job` or `new_name`. It fails to provide format, constraints, or examples, leaving the agent without guidance on how to fill these fields correctly.

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') and the resource ('top-level job'). It provides a specific verb and resource, but does not differentiate from sibling tools like `jenkins_create_job` or `jenkins_update_job_config`, which could also be considered for similar tasks.

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 mentions required flags ('write and job-config') but gives no guidance on when to use this tool over alternatives. There is no 'when to use' or 'when not to use' context, leaving the agent without decision support.

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