query_items

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

No annotations are provided, so the description must disclose behavioral traits. It mentions querying and traversal depth but does not explicitly state that it is read-only, safe to call repeatedly, or what happens if patterns match nothing. It lacks explicit safety or idempotency claims.

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 short: one-line purpose, then clear bullet-style Args, then Returns. Every sentence is informative and there is no fluff. Front-loaded with the main purpose.

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?

The tool has an output schema (present but not shown) and 4 optional parameters. The description covers what the tool does and each parameter. It could mention that patterns are combined and optional, but it's sufficiently complete given the output schema handles return details.

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%, but the description fully explains each parameter: class_pattern is 'The pattern of the _class', etc., and folder_depth is 'The maximum depth of folders to traverse. If None, traverses all levels.' This adds significant meaning beyond the raw schema.

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 'Query items from Jenkins' with specific filter parameters (class, fullname, color patterns, folder depth). This distinguishes it from sibling tools like get_all_items (unfiltered) and get_item (single item).

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 implies filtering use via patterns but does not explicitly state when to use this tool over get_all_items or other query tools. No 'use this when' or 'consider alternatives' guidance is provided.

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