zabbix_delete_services

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

The description merely restates the mutation ('Delete') without any additional behavioral disclosure. There are no annotations to fall back on, so the description should explain irreversibility, cascading deletions, permissions, or error behavior, but it does not.

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 short sentence that states the operation without verbosity or filler. It is front-loaded and easy to parse.

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 simplicity (one array parameter, no output schema), the description is minimally sufficient to select and invoke the tool, but it omits consequences of deletion and expected return state. Compared to well-documented alternatives, it lacks important situational context but is not severely incomplete due to the complete schema.

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 input schema fully documents the single 'serviceids' parameter with a description, so the tool description adds no extra semantic value. Since schema coverage is 100%, the baseline of 3 applies; there is no need for the description to elaborate.

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 'Delete business services from Zabbix' uses a specific verb and resource, clearly distinguishing it from sibling delete tools like zabbix_delete_users or zabbix_delete_templates by naming 'business services' specifically.

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 like zabbix_create_service or zabbix_update_service. The description does not state prerequisites, whether deletion is permanent, or how to handle dependencies. This is a minimal statement with no contextual usage guidance.

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