zadig_build_template_list

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

With no annotations, the description carries the full burden of disclosing behavioral traits, but it only says 'List/search' without confirming read-only behavior, output shape, pagination, or side effects. The description adds little beyond the tool's name, leaving the agent to assume safety and behavior.

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 concise sentence with no filler or redundant information. It front-loads the action and resource, which is efficient, though it is so terse that it sacrifices useful detail.

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 list/search tool, the description is minimally viable: it names the action and resource, and an output schema exists to define returns. However, key contextual gaps remain—what 'include_raw' does, how search behaves, and whether this is a safe read-only operation—so it is not fully complete.

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 either parameter. 'List/search' loosely hints that 'query' performs searching, but 'include_raw' is completely unexplained, and the description adds no real semantics beyond the raw schema titles and defaults.

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 states a clear action ('List/search') and a specific resource ('build template store templates'), which distinguishes it from sibling tools like zadig_build_template_get or zadig_build_template_reference. It could be more explicit about what distinguishes these templates from general build definitions, but the core purpose is understandable.

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 is provided about when to use this tool versus alternatives such as zadig_build_template_get or zadig_build_list. There are no context cues, prerequisites, or exclusions, so an agent must infer usage solely from the name and minimal description.

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