zabbix_gerenciar_grupos_hosts

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

No annotations are supplied, so the description carries the full burden. It admits the tool deletes host groups but discloses nothing about irreversibility, cascade effects on hosts/templates already in the group, required permissions, or the approval-token gating implied by the `token_aprovacao` parameter — 'verificações necessárias' is a placeholder, not disclosure.

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 front-loaded sentence that gets to the verbs and resource immediately with no padding. The only waste is the unexplained leading '74.' numbering artifact, which belongs to a catalogue listing rather than a tool definition.

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 need not be explained. But for a four-parameter, unannotated mutation tool that can delete resources and requires an approval token, the description omits exactly the operational detail an agent needs — valid `acao` values and the approval workflow — leaving it materially incomplete.

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?

All four parameters have 0% schema description coverage, and the description supplies no semantic mapping: the allowed values of `acao`, the create-vs-update meaning of `nome` vs `groupid`, and especially the purpose of `token_aprovacao` are left entirely undocumented. Only a loose implication that the three verbs correspond to `acao` values can be drawn.

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 specific verbs (create, update, delete) against a specific resource (host groups), which lets an agent distinguish it from the read-only sibling zabbix_listar_grupos_hosts and from zabbix_gerenciar_grupos_templates. It never explicitly names those siblings, so differentiation is inferred from the resource noun rather than stated.

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 pick this over zabbix_listar_grupos_hosts or the template-group equivalent, and no explanation of which `acao` value triggers which of the three operations. The phrase 'com as verificações necessárias' hints at preconditions but never says what they are or when they block the call.

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