zabbix_delete_templates

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

With no annotations, the description must disclose behavioral traits. It conveys that the tool deletes templates but omits critical details such as irreversibility, cascading effects on linked hosts or dependent items, required permissions, or error behavior. This is a significant gap for a destructive operation.

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 one sentence and thus highly concise and front-loaded. However, it essentially restates the tool name, providing no extra information beyond what the name already conveys, so it does not add value commensurate with its brevity.

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?

The description is inadequate for a destructive tool with no annotations and no output schema. It fails to explain the consequences of deletion, whether templates must be unlinked first, or what becomes of associated entities, leaving the agent with incomplete information to reason about tool invocation.

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 describes the only parameter (templateids) as an array of IDs, so the description adds no additional meaning. According to the rubric, high schema coverage (100%) establishes a baseline of 3, which is appropriate here.

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 the resource (templates), making the tool's purpose unambiguous. It is distinct from sibling tools that delete other entities, though it does not explicitly differentiate from related actions like unlinking templates.

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 (e.g., zabbix_unlink_templates_from_host). The description only states the action without any context about prerequisites, use cases, or conditions that would help an agent choose between this and similar tools.

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