trigger_build

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

No annotations are provided, so the description carries the full burden. It does disclose the queue-polling behavior and wait default, which is useful. However, it does not explain what happens on timeout, what wait=False does, what the tool returns, or any prerequisites/auth requirements.

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 three concise sentences with no filler. The first sentence states the core purpose, the second adds a key behavioral detail, and the third routes to the right sibling alternative.

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?

With no output schema and no annotations, the description should cover return behavior and side effects more fully. It does not mention what the tool returns, the behavior when wait=False, or what happens when the timeout expires. The description is a good start but not complete enough for confident use.

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%, so the description must compensate for explaining parameters. It adds meaning for `parameters` by saying they use raw Jenkins names and confirms the `wait` default. But it does not describe `timeout` semantics/units or the required `job_name` parameter.

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 uses a specific verb and resource, 'Trigger a build,' and immediately clarifies that it operates on raw Jenkins parameter names. This distinguishes it from the higher-level deploy sibling, so an agent can tell what the tool does and how it differs.

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 explicitly states when to use this tool versus the alternative: if a higher-level deploy with friendly names is needed, use deploy(). It also clarifies that wait=True is the default and polls the queue, giving clear context for invocation.

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