zabbix_delete_actions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a mutating operation but does not mention irreversibility, required permissions, what happens if action IDs are invalid, or any side effects. For a delete operation, this is a significant gap in transparency.

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, focused sentence that immediately conveys the action and resource. It contains no filler or redundant phrasing, making it highly concise and front-loaded.

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 lack of annotations and output schema, the description is too sparse to be contextually complete. It does not explain the effect of deletion, potential errors, or any behavioral nuances. While the parameter is well-schema'd, the overall context (e.g., irreversibility, permissions) is missing.

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 has 100% coverage with the parameter description 'Array of action IDs to delete', so the schema fully documents the parameter. The description adds no additional meaning or context about the parameter. Baseline of 3 is appropriate since the schema handles the semantics.

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 verb ('Delete') and resource ('actions'), which is a specific Zabbix object type. It distinguishes itself from sibling tools by naming the resource, but it does not elaborate on what 'actions' are or the exact scope, so it is clear but not fully differentiated from other delete tools.

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 does not mention prerequisites, when it is appropriate to delete actions, or any exclusions. The only implied usage is that it deletes actions, but there is no explicit context or comparison to create/update actions.

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