zabbix_desassociar_templates_host

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

No annotations are supplied, so the description carries the full disclosure burden for a mutating operation. It does not say the operation is destructive, what 'limpeza/clear' actually deletes (items, triggers, history), whether it can be undone, or what permissions are required. Only the vague phrase 'opção de limpeza' hints at consequence.

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 with the action front-loaded, but the leading '19.' is a leftover list artifact that adds noise, and the extreme brevity here comes at the cost of substance rather than from 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 need no explanation, but for a destructive mutation with zero annotations and zero parameter descriptions the definition is thin. An agent would not know the blast radius of choosing clear=true or how to format the template ID list before calling.

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% across three parameters, so the description must compensate and does not. 'Limpeza (unlink / clear)' vaguely points at limpar_itens_triggers but never explains what clearing removes, and hostid and templates_ids (format, single vs array, ID vs name) are 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 verb and resource ('Remover associações de templates' / remove template associations) and adds the cleanup option, which is enough to distinguish it from the sibling zabbix_associar_templates_host. It does not explicitly name that sibling, but the add/remove verb pair makes the intent unambiguous.

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 statement of when to use this tool versus zabbix_associar_templates_host or the broader template-management tools, and no prerequisites (e.g. host must exist, templates must be currently linked). The parenthetical '(unlink / clear)' gestures at a decision point but never explains which mode to choose.

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