jenkins_list_queue

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'list visible' but does not explain visibility criteria, whether authentication is required, or any side effects. It is a read operation by implication, but the description is too brief to be transparent.

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 at one sentence, but it omits essential context like parameter usage. It is not verbose, but it sacrifices utility for brevity.

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 one optional parameter and an output schema, the description should at least explain the parameter's role and the type of data returned. It does not, making it incomplete for practical use. The output schema partially compensates, but the description still falls short.

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 single parameter 'tree' has a default value but is not described in the description. The schema has 0% description coverage. The agent has no guidance on how to use the 'tree' parameter (e.g., for field filtering), making it difficult to invoke correctly.

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 'List visible Jenkins queue items' clearly uses a specific verb ('list') and resource ('visible Jenkins queue items'). It distinguishes from siblings like jenkins_get_queue_item and jenkins_cancel_queue_item, which operate on individual items. However, it lacks explicit mention that it lists all queue items or that it's a read operation.

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 is provided on when to use this tool versus alternatives. For example, it does not clarify when to use jenkins_list_queue versus jenkins_get_queue_item for a specific item. There is no mention of prerequisites or context.

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