zabbix_drule_delete

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

With no annotations, the description should disclose behavioral traits. It only states it calls the delete method, implying destruction, but no details about irreversibility, permissions, or side effects. The description fails to provide sufficient transparency beyond the name.

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 sentence, which is concise, but it is underspecified and does not earn its place. It adds no value beyond the tool name, making it ineffective.

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?

Despite an output schema, the description omits context such as prerequisites, result format, or relation to siblings. For a deletion tool with many sibling entity types, this lack of completeness severely hinders correct usage.

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?

Schema description coverage is 0%, and the description does not explain the 'params' parameter. The agent has no guidance on what properties the object should contain, leaving invocation ambiguous.

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 states 'Zabbix API drule.delete method', which indicates the tool deletes a discovery rule (drule). It provides the verb and resource, but lacks scope or details to differentiate from sibling tools like drule_create or drule_update. It is minimally clear but not misleading.

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 on when to use this tool versus alternatives (e.g., drule_update, drule_create). No prerequisites, context, or when-not-to-use information is provided, making it difficult for an agent to decide when to invoke it.

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