create_pipeline_job

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

With no annotations, this description carries the full burden and does notable work: Groovy sandbox execution, required plugins, credential-ID-only guidance against plaintext secrets, and a MCP_MAX_REQUEST_BYTES size constraint. It stops short of stating idempotency (behavior when the job already exists) or the response shape.

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?

Four short sentences, purpose front-loaded, each sentence contributing a distinct operational fact. No redundancy or padding.

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 mutation tool with zero annotations and no output schema, the description covers environment, security, and size constraints well. It leaves gaps on return values and what happens on name collision, but is otherwise sufficiently complete.

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 coverage is 0%, so the description must compensate. It adds genuine content constraints for the jenkinsfile parameter (sandbox, credential references, size limit), but job_name and description remain undocumented beyond self-explanatory titles, so coverage is partial.

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?

States a specific verb (Create), resource (Pipeline job), and source format (inline Jenkinsfile). The 'inline Jenkinsfile' scoping cleanly separates it from create_job_from_xml and create_multibranch_pipeline without needing to name them.

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?

Prerequisites are spelled out (workflow-job and workflow-cps via workflow-aggregator), which implies the environment needed to use it. However, it never says when to prefer this over create_job_from_xml or create_multibranch_pipeline, so alternative selection is left to inference.

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