jenkins_create_job

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

No annotations exist, so the description carries full burden. It discloses the need for specific flags (write, job-config) and that it creates a top-level job. However, it does not mention if the tool overwrites existing jobs, error handling, or return values.

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 sentence with a prerequisite note, no filler words, and all information is front-loaded. It is appropriately sized for a simple create operation.

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 lack of annotations and minimal schema descriptions, the description is insufficient. It does not explain the output (though an output schema exists), error scenarios, or behavior if a job with the same name exists. More details are expected for a creation 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?

With 0% schema description coverage, the description must compensate. It hints that 'config_xml' is the config content via 'from config.xml', but does not explain the 'name' parameter (e.g., format, uniqueness). This adds minimal value beyond the parameter names.

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 tool creates a top-level job from config.xml, using specific verb 'create' and resource 'job from config.xml'. This distinguishes it from siblings like jenkins_get_job, jenkins_delete_job, and jenkins_copy_job.

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?

It mentions required flags ('write' and 'job-config'), which provides some usage guidance. However, it does not explicitly state when to use this tool versus alternatives like jenkins_update_job_config or when the job already exists.

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