jenkins_trigger_build

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

With no annotations, the description must disclose behavioral traits. It fails to mention that triggering a build is a mutation, whether it's asynchronous, what authentication is needed, or what the response contains (e.g., build number or queue id).

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 with no verbosity. However, it may be too brief, missing important details that could fit without much length increase.

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 no output schema and no annotations, the description should cover inputs, behavior, outputs, and side effects. It only covers the basic action, omitting crucial context like return value, asynchronous nature, and error handling. 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?

Schema description coverage is 100% with both params documented in the schema. The description adds no meaning beyond 'optionally with parameters', which is already evident from the schema. Baseline score of 3 applies.

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 it triggers a Jenkins job build, which distinguishes it from sibling tools that retrieve data (e.g., jenkins_get_build, jenkins_list_jobs). The verb 'trigger' is specific and the resource 'Jenkins job build' is unambiguous.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites (e.g., job must exist, permissions required). The description implies usage for triggering but doesn't mention exclusions or context.

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