zadig_build_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List/search' and does not clarify whether the operation is read-only, what the output contains, whether results are paginated, or what the 'raw' mode returns. The description is not inaccurate but is severely under-disclosing.

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 one short, front-loaded sentence with no redundant words. It is appropriately concise, though it may be too terse to serve as a complete guide for a tool with five parameters.

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?

For a tool with five parameters, no annotations, and a large sibling set, the description is too thin. It does not cover pagination, project scoping, raw output behavior, or when to use this tool over alternatives, leaving meaningful gaps for correct invocation with non-default parameters.

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% and the description does not explain the five parameters. The 'search' verb weakly hints at the query parameter, but there is no explanation of project_key filtering, pagination defaults, or the meaning of include_raw, leaving the agent to guess.

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 ('List/search') and the resource ('Zadig build configurations'). This is sufficient to understand the basic purpose and distinguish it from a single-get operation, though it does not explicitly differentiate it from sibling list-like tools such as zadig_build_template_list.

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?

There is no guidance on when to use this tool rather than zadig_build_get, zadig_build_template_list, or zadig_service_search. The description does not mention when filtering by project_key or setting include_raw would be appropriate, leaving the agent to infer usage from parameter names alone.

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