Search Buildsets

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

Annotations already indicate safe read-only, idempotent, non-destructive behavior. The description adds valuable context about pagination (limit, skip) and the behavior of 'include_builds' (fetching full details, performance impact). No contradictions.

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 well-structured: a one-line purpose followed by a bullet list of parameters with clear explanations. The 'include_builds' parameter includes additional guidance. Every sentence serves a purpose, with no wasted words.

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 tool has 14 parameters, no required ones, and an output schema exists, the description covers all parameters and provides enough context for usage. It explains filtering, pagination, and the trade-off of 'include_builds'. No need to describe return values since output schema handles that.

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 schema has 0% description coverage, meaning no parameter descriptions in schema. The tool's description compensates fully with detailed explanations for each parameter, including format examples (ISO 8601 for dates) and default behavior. This adds significant meaning beyond what the schema provides.

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 'Search buildsets (groups of builds triggered by a single event).' It uses a specific verb and identifies the resource. Among siblings, 'get_buildset' retrieves a single buildset, so this tool is differentiated as a listing/search tool.

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 provides filtering parameters and explains the 'include_builds' parameter with usage guidance ('Saves a separate get_buildset call per result... Best with limit <= 5'). It implies when to use this tool vs. 'get_buildset' but does not explicitly state alternatives or exclusions for general use.

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