zabbix_auditlog_delete

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

No annotations are present, and the description does not disclose any behavioral traits beyond 'delete'. It fails to mention if the operation is irreversible, requires authentication, or has any side effects on dependent data.

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 that is front-loaded and contains no fluff. However, it is too terse and omits essential information, making it borderline under-specified rather than concisely complete.

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 the tool has no annotations, a vague parameter schema, and multiple sibling tools, the description fails to provide enough context for safe and correct usage. It does not explain the output schema or any constraints.

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 a single parameter 'params' with no description or constraints. Schema description coverage is 0%. The description adds no meaning to the parameter, leaving the agent without guidance on what to provide.

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 identifies the tool as performing a delete operation on the auditlog resource via the Zabbix API. It distinguishes from sibling tools like zabbix_auditlog_get or zabbix_auditlog_create. However, it lacks detail about what auditlog deletion entails.

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 compared to alternatives. There is no mention of prerequisites, permissions, or scenarios where deletion is appropriate. Sibling tools with similar CRUD operations offer no differentiation.

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