zabbix_listar_templates

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

No annotations are provided, so the description carries the full burden. 'Listar' weakly implies a read-only operation, but nothing is said about pagination behavior (limite defaults to 50, offset to 0), whether results are truncated, or how expensive the association lookup is. For a no-annotation tool this is a substantial gap.

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?

A single short sentence is efficient, but the leading '75.' is an unexplained artifact that adds noise to the front of the description. The brevity stems from under-specification rather than disciplined editing.

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?

An output schema exists, so return-value shape need not be described, but the description still omits filtering semantics and pagination defaults for a three-parameter listing tool. An agent would have to guess how to scope a query or page through results.

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% for all three parameters. The description does not explain whether 'nome' is an exact match, substring, or regex filter, nor does it mention that 'limite'/'offset' control paging. The parameter names are the only guide, which is insufficient.

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 verb 'Listar' and resource 'templates' are clear, but 'associações' is undefined — it is unclear whether this means host-template links, template group links, or something else. The description also does not distinguish it from close siblings like zabbix_consultar_template, zabbix_listar_grupos_templates, or zabbix_auditar_cobertura_templates.

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 list tool versus zabbix_consultar_template (single template lookup) or zabbix_recomendar_templates. No prerequisites, no exclusions, and no indication of when the association data is relevant.

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