get_all_queue_items

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

With no annotations, the description carries full burden for behavioral transparency. It only states the action and return type, omitting details like read-only nature, performance impact, or what constitutes 'queue items' (e.g., waiting builds).

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 very short with one line of purpose and a Returns section. No extraneous content, but could be more front-loaded with the return type. High conciseness with minor structural improvement possible.

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 parameters and an output schema, the description covers the basic purpose. However, missing context about the nature of queue items (e.g., are they build requests?) and possible side effects (none expected). Adequate for a simple tool but feels sparse.

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?

Input schema has no parameters (100% coverage), so the description adds no parameter information. Baseline for zero parameters is 4, but the description could clarify the meaning of the returned list (e.g., queue items as pending builds). Hence score 3.

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 the action ('Get all items') and the resource ('Jenkins queue'), using a specific verb and resource. It implicitly distinguishes from 'get_queue_item' (singular) but does not explicitly differentiate from sibling tools.

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 vs alternatives (e.g., get_queue_item, get_all_builds). No context on prerequisites or typical use cases provided.

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