zabbix_get_hostgroups

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'with filtering and output options,' which is a summary of the schema and does not reveal behavior such as whether all host groups are returned when no filters are applied, whether authentication is required, or whether the operation is safe/read-only. The name 'get' implies read-only, but the description itself adds no behavioral context.

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?

The description is a single, focused sentence that avoids superfluous language, making it easy to parse quickly. It front-loads the core function.

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?

The tool has a comprehensive schema covering all parameters, but the description offers minimal context. It does not mention return format, typical use cases, or safety characteristics, and there is no output schema. However, for a straightforward get operation, the combination of name, description, and schema is probably sufficient for correct invocation, though additional context would improve it.

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 100%, so each of the 8 parameters is already documented. The description's mention of 'filtering and output options' adds no additional semantic value beyond what the schema provides.

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 description uses the specific verb 'Get' and identifies the resource 'host groups' within Zabbix, and mentions 'filtering and output options' which maps to the schema. This clearly distinguishes it from sibling tools like create/update/delete hostgroups.

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?

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of related tools. It is a bare statement of functionality, so an agent receives no help in choosing between this and other Zabbix getters or mutation tools.

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