Delete a Zendesk trigger by ID to remove automation rules. Specify the trigger ID to permanently delete it from your account.
Delete a trigger
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Trigger ID to delete |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no additional context about side effects, irreversibility, or what happens to related data. It merely restates the action without enriching the agent's understanding.
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, concise sentence with no wasted words. It is appropriately minimal for the tool's simplicity and fully 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?
The tool is simple with one parameter and clear annotations. The description covers the essential action but omits details like error behavior or return format, which, while not critical for a delete operation, would enhance completeness. Given no output schema, a slightly richer description could be beneficial.
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 fully documents the single 'id' parameter with type and description (100% coverage). The tool description adds no extra meaning beyond what the schema provides, so the baseline score of 3 applies.
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 the action 'Delete' and the resource 'trigger' clearly. It is specific enough to identify the operation, though it does not differentiate from sibling tools beyond the obvious (e.g., get_trigger, update_trigger).
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 like update_trigger or delete_automation. There is no mention of prerequisites, exclusions, or conditions that would make this tool the correct choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.