get_running_builds

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

With no annotations, the minimal description fails to disclose behavioral traits beyond the basic function. No mention of read-only nature, scope (all Jenkins vs folder-level), or any constraints. The description adds no value over the tool name.

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 extremely concise with two short sentences. It front-loads the core purpose and is free of wasted words. Every sentence serves a clear function.

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 presence of an output schema (reducing burden to explain returns), the description is adequate but minimal. It covers the basic purpose but lacks any additional context about the tool's behavior within the Jenkins ecosystem, such as what qualifies as 'running' or performance considerations.

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?

The input schema has zero parameters (100% coverage), so the description has no burden to explain parameters. Baseline for 0 parameters is 4, and the description adds no additional meaning, which is acceptable as there are no parameters to clarify.

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 'Get all running builds from Jenkins' with a specific verb and resource. It distinguishes from sibling tools like 'get_build' (specific build) and 'get_all_queue_items' (queue items), making the purpose 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 (e.g., get_build, get_all_queue_items). The description lacks any usage context, prerequisites, or exclusions, leaving the agent without decision support.

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