jenkins_trigger_build_with_parameters

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

No annotations provided, so description must carry full burden. It mentions it triggers a build (write operation) but does not disclose side effects, return behavior, or what happens on failure. With an existing output schema, description adds minimal value beyond stating the action.

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?

Description is one short sentence plus a prerequisite, which is concise. Slightly benefits from a bit more detail on parameters or behavior, but overall front-loaded and efficient.

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?

Lacks behavioral details, return value explanation, and differentiation from sibling tools. With 3 parameters and an output schema, description should provide more context. The prerequisite is useful but overall incomplete.

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%; no parameter descriptions in schema. Description does not explain parameters (job, parameters map, delay) beyond their names. Critical details like valid values, format, or defaults for delay are missing.

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 the action (trigger) and resource (parameterized job build). The name and description distinguish it from sibling 'jenkins_trigger_build' by including 'with parameters'. The prerequisite requirement adds context.

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?

Description states the requirement for JENKINS_MCP_ENABLE_WRITES=1, which is important. However, it does not explicitly guide when to use this tool versus the alternative 'jenkins_trigger_build' or other job manipulation tools. Usage context is implied but not explicit.

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