Query Zabbix host groups with host counts, filter by name, and limit results to inspect group inventory or triage hosts.
Host groups with host counts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| search | No | Name filter (wildcard allowed) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description contributes only that results include host counts, which is a small return-shape hint. It says nothing about pagination, default limits, ordering, or completeness of the result set.
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?
There is no padding or wasted wording, but the text is a fragment rather than a properly sized description, so its brevity comes from under-specification rather than efficiency. It is front-loaded but nearly empty.
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?
With no output schema, the description should at least explain what a host group record includes, how many are returned by default, and how filtering behaves. Given the tool exposes pagination and search parameters, the one-line fragment leaves the agent with unresolved questions before calling 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 50%: 'search' is documented as a wildcard name filter, but 'limit' has no description beyond its default of 50 and max of 200. The description does not mention either parameter, so it fails to compensate for the undocumented limit or clarify filtering semantics.
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 is a bare noun phrase, "Host groups with host counts." It restates the resource encoded in the name (list_host_groups) and adds only that host counts are included. There is no verb and no differentiation from siblings such as search_hosts or get_host_details, so an agent learns little beyond the tool name.
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 when-to-use guidance, no when-not-to-use, and no mention of alternatives like search_hosts or get_host_details. An agent must infer from the name alone that this is a listing/browsing tool rather than a search or detail lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.