zabbix_listar_hosts

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

No annotations are provided, so the description carries the full burden and does not discharge it. It does not disclose pagination defaults (limite=50, offset=0), result caps, or the fact that it is a read-only operation; 'listar' implies read-only but nothing about truncation or volume limits is stated.

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 with no filler; the leading list item number '11.' is a leftover artifact but does not impede comprehension.

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, and the tool is a simple paginated list. However, with 5 undocumented parameters, an unhelpful integer 'status' with no enumerated values, and a phantom 'disponibilidade' filter, the description is not complete enough to call it confidently.

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%, so the description must compensate and only partially does: it names nome, grupo and status but says nothing about limite and offset. Worse, it advertises a 'disponibilidade' filter that has no corresponding parameter, which can mislead an agent into passing an unsupported argument.

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 ('Listar hosts') plus the filter dimensions, so an agent knows exactly what it returns. It does not distinguish itself from siblings like zabbix_consultar_host (single host) or zabbix_listar_itens, leaving that routing to inference.

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?

Only an implied usage ('listar hosts com filtros'), with no statement of when to prefer this over zabbix_consultar_host or zabbix_listar_grupos_hosts. No prerequisites, no exclusions, no pagination guidance despite limite/offset being present.

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