zabbix_host_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It labels the operation as 'Deletes' but does not disclose that deletion is typically irreversible, may cascade to dependent items (e.g., triggers, items), or may require specific permissions. This lack of warning for a destructive action is a significant gap.

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, clear sentence with no redundant words. Every word earns its place, and it is front-loaded with the primary action and target.

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?

For a simple tool with one parameter and no output schema, the description states the core function. However, given the destructive nature, the lack of any warning about non-reversibility or dependencies is a clear gap. The schema handles parameter detail, but the description fails to add the behavioral context needed for safe use, making it only minimally viable.

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 already provides 100% coverage of parameters, including a description for 'hostids' ('Array of host IDs to delete'). The tool description adds no extra meaning beyond the schema, so the baseline of 3 is appropriate.

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 ('Deletes') and the resource ('hosts from Zabbix'), and distinguishes it from sibling tools like zabbix_host_get, zabbix_host_create, and zabbix_host_update. It also conveys the flexibility of 'one or more', which is a specific scope detail.

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 prerequisites, and no exclusions. It merely states the action. For a deletion tool, it would be helpful to mention that this should be used for permanent removal, not for temporary disabling, and that other tools should be used for updates.

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