zabbix_get_templates

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

With no annotations, the description carries the full burden of disclosing side effects and behavioral traits. It only says 'Get templates' and mentions filtering/output, which implies read-only but never explicitly states it. It does not mention authentication requirements, pagination, default limits, or any side effects, leaving key behavioral aspects undisclosed.

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 sentence with no redundant words, effectively front-loading the core action. It is concise and well-structured, though the brevity sacrifices depth; still, it avoids fluff and is appropriately scoped for a tool with rich schema documentation.

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's complexity (11 parameters, no annotations, no output schema), the description is under-specified. It does not explain return values, default output fields, sorting behavior, or how filters interact. The description is not completely inadequate but leaves significant gaps that an agent would need to infer from the schema alone.

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 input schema covers 100% of the 11 parameters with individual descriptions, so the baseline is 3. The description's reference to 'filtering and output options' maps loosely to `filter`, `search`, and `output` parameters but adds no new meaning beyond what the schema already provides. It does not clarify parameter formats, defaults, or relationships.

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 uses a specific verb 'Get' and a clear resource 'templates from Zabbix', immediately distinguishing it from sibling tools like zabbix_create_template or zabbix_delete_templates. It also mentions 'filtering and output options', which adds useful functional scope without ambiguity.

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 no explicit guidance on when to use this tool versus alternatives such as zabbix_host_get or zabbix_create_template. It doesn't state exclusions or prerequisites, and while the name implies a read operation, no contextual hints about preferred use cases are provided.

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