zabbix_delete_scripts

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

There are no annotations to indicate safety profile, and the description does not disclose behavioral traits such as irreversibility, potential impacts on running script executions, or permission requirements. For a delete operation, this lack of transparency 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 that front-loads the action and resource. It contains no fluff and is appropriately sized for the simple functionality.

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 that this is a destructive operation with no annotations and no output schema, the description is incomplete. It fails to mention that deletion is permanent, lacks usage guidance, and does not describe any response or error conditions, leaving the agent without essential context for safe 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 provides 100% coverage with the description 'Array of script IDs to delete' for the scriptids parameter. The tool description adds no further meaning, but the schema already sufficiently documents the parameter, so a baseline score 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 'Delete scripts from Zabbix' uses a specific verb and resource, clearly indicating the action. It distinguishes itself from sibling tools like zabbix_get_scripts, zabbix_create_script, and zabbix_update_script by focusing solely on deletion.

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, nor are any prerequisites or caveats mentioned (e.g., scripts in use cannot be deleted, deletion is permanent). The description lacks any context about appropriate usage scenarios.

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