zabbix_gerenciar_grupos_templates

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

No annotations are provided, so the description bears the full disclosure burden, but 'gerenciar' leaves open whether this creates, renames, or deletes groups, what permissions are required, and whether operations are destructive. The only added context is the version-dependent resource naming, which is helpful but far from sufficient for a mutation-capable 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?

It is a single front-loaded sentence with no filler, but the leading '79.' is noise and the brevity comes at the cost of under-specification rather than efficiency.

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 values needn't be explained, but with no annotations, 0% parameter coverage, and a manage/consult dual mode, the description omits everything an agent needs to invoke it correctly beyond the resource name.

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 never mentions either parameter. The meaning of 'acao' (default 'listar' but no enum or allowed values) and whether 'nome' is a filter for listing or the target for management is entirely undocumented.

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?

States a specific resource (template groups) and the operations (consult and manage), plus the useful version nuance that Zabbix calls these templategroup or hostgroup depending on version. It is distinguishable from the host-group siblings via the resource name, though the verb pair 'consultar e gerenciar' is broad.

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 on when to use this instead of zabbix_listar_grupos_hosts or zabbix_gerenciar_grupos_hosts, and no explanation of which 'acao' value corresponds to consult versus manage. The agent must guess from the tool name alone.

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