zadig_build_template_reference

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

With no annotations, the description carries the disclosure burden. 'List' clearly indicates a read-only query rather than a mutation, and the 'reference' wording explains the relationship being reported. It does not detail edge cases such as empty results or whether both identifiers are filters, but the output schema likely covers return structure.

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 a single, front-loaded sentence with no filler, and every word contributes to identifying the operation and scope.

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 simple two-parameter list tool with an output schema, the description is adequate but incomplete: it omits parameter usage guidance and does not clarify the intended workflow. It is sufficient to identify the operation but not fully enough to invoke it confidently without schema inspection.

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 template_id or template_name. The names are self-explanatory, but an agent cannot tell whether one or both are needed, which takes precedence, or what formats are expected.

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 names a specific action ('List') and a clear resource ('build configurations') plus the filter ('reference one build template'). This is distinct from siblings like build_template_get or build_list, which serve different purposes.

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 use case is implied: call this tool when you need to know which build configurations depend on a given template. However, the description does not explicitly say when to prefer it over build_list, build_template_get, or build_update_from_template, nor does it mention preconditions or alternatives.

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