zadig_build_template_get

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'one' and 'exact name,' but does not clarify that exactly one of template_id or template_name should be provided, what happens if both are omitted, or behavior when no match is found. These are material gaps for a retrieval tool.

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 sentence with no filler, front-loading the action and resource. It loses a point for the awkward 'store template' wording, which could confuse rather than clarify.

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 output schema covers return values, so that gap is acceptable. However, the description fails to specify that at least one lookup parameter is needed and does not distinguish this tool from alternatives, leaving an agent potentially unsure how to invoke it correctly. For a simple get tool this is a notable omission.

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%, so the description must compensate. It does map the two parameters to lookup keys and adds that name matching must be exact, but it provides no further detail about ID format, precedence, or constraints. This is minimal but not useless.

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 ('Get one') and resource ('build template store template') with lookup criteria ('by id or exact name'). It is distinguishable from sibling list/mutation tools, though the phrase 'store template' is awkward and slightly obscures the intended resource.

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 usage for retrieving a single template by identifier or exact name, as opposed to listing all templates or mutating one. However, it does not explicitly name alternatives or state when not to use this tool, leaving the routing decision mostly to inference.

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