zabbix-mcp-server

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

No annotations are provided, so the description carries the full burden. It states the tool deletes templates and returns a JSON result, but fails to disclose critical behavioral traits: it doesn't mention that deletion is destructive and likely irreversible, specify authentication or permission requirements, or describe error handling. For a destructive operation with zero annotation coverage, this leaves significant 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 appropriately sized and front-loaded, with the core purpose stated first ('Delete templates from Zabbix'), followed by parameter and return details. Each sentence adds value, though the structure could be slightly improved by integrating the return note into the main sentence for better flow.

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 the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It covers the basic action and parameter but omits critical context: no details on the JSON return structure, error conditions, side effects on related resources, or safety warnings. For a deletion tool, this leaves the agent under-informed.

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?

The schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'templateids' is a 'List of template IDs to delete', which clarifies the parameter's purpose beyond the schema's array of strings. However, it doesn't provide format details (e.g., ID structure) or constraints (e.g., minimum list size), leaving some ambiguity. With one parameter and partial compensation, this meets the baseline.

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 ('Delete') and resource ('templates from Zabbix'), making the purpose unambiguous. It distinguishes from siblings like template_create, template_get, and template_update by specifying deletion. However, it doesn't explicitly differentiate from other deletion tools like host_delete or maintenance_delete beyond the resource type.

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 guidance is provided on when to use this tool versus alternatives. While it's implied this is for deleting templates specifically, there's no mention of prerequisites (e.g., templates must exist), consequences (e.g., irreversible action), or when to choose other tools like host_delete for different resources. The description lacks explicit usage context.

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