zabbix-mcp-server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation (implying mutation) and mentions a JSON-formatted return, but lacks critical details: whether it requires specific permissions, if changes are reversible, error handling for invalid groupids, or rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 efficiently structured with a clear purpose statement followed by bullet-pointed Args and Returns sections. Every sentence adds value: the first states the action, and the subsequent lines document parameters and output. There is no redundant or verbose content.

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?

Given 2 parameters with 0% schema coverage and no output schema, the description partially compensates by listing parameters and noting a JSON return. However, as a mutation tool with no annotations, it lacks details on permissions, side effects, error cases, or output structure. It's minimally adequate but has clear gaps for safe and effective use.

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. It explicitly lists both parameters (groupid, name) with brief explanations ('Group ID to update', 'New group name'), adding meaningful semantics beyond the bare schema. This covers all parameters adequately, though it doesn't detail format constraints (e.g., groupid format, name length).

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 clearly states the action ('Update') and resource ('existing host group in Zabbix'), making the purpose immediately understandable. It distinguishes from siblings like hostgroup_create and hostgroup_delete by specifying it updates existing groups rather than creating or deleting them. However, it doesn't explicitly contrast with hostgroup_get (read vs. write).

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. It doesn't mention prerequisites (e.g., needing an existing groupid), compare with host_update for host-level changes, or specify scenarios where hostgroup_update is appropriate over hostgroup_create or hostgroup_delete. Usage context is implied but not explicitly stated.

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