item_delete

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

Annotations already flag this as destructive and non-idempotent. The description adds useful behavioral context by stating that deletion is permanent and that historical data removal 'typically' happens but depends on Zabbix configuration, which extends beyond the annotation values.

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?

Two concise, front-loaded sentences. The first gives the primary action and target; the second adds an important consequence about historical data. No filler or redundant restatement of the schema.

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?

For a simple single-parameter tool with a destructive annotation and an output schema, the description covers the core behavior, permanence, and data-history implication. It could more fully discuss failure behavior with invalid item IDs, but the required information for calling it correctly is present.

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 already fully documents itemids as 'Item IDs to delete' with 100% coverage. The description adds little beyond the schema, though it does reinforce that one or more items can be removed, consistent with the minItems:1 constraint.

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 and resource: 'Delete items from Zabbix' and 'Permanently removes one or more items from monitoring.' It is unambiguous and naturally distinguishes the tool from sibling deletion tools like trigger_delete or maintenance_delete.

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 clearly implies this tool is for removing items when deletion is the goal, but it does not state when not to use it, mention softer alternatives like item_update or disabling an item, or reference sibling tools by name. Context is present but exclusion criteria are implicit.

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