zda_delete_trigger

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

No annotations provided, so the description alone must convey behavior. It explains the guarded deletion pattern (preview then apply), which is critical. However, it does not mention permissions, error handling, or reversal options.

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 sentences: first states purpose, second explains guarded usage. No wasted words, front-loaded with purpose.

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 delete tool with no output schema or annotations, the description covers the essential guard mechanism. It could mention expected outcomes or failure modes, but is adequate given the simple parameter set.

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 coverage is 50% (id and require_confirm). The description adds meaning to require_confirm by detailing its role in the guarded flow. The id parameter's semantics are not expanded, but the schema already describes it as 'Numeric object ID'.

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 'Delete a Zendesk trigger', specifying the verb 'Delete' and the resource 'Zendesk trigger'. This distinguishes it from sibling tools like zda_delete_automation or zda_delete_group.

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 provides explicit two-step usage: preview without require_confirm, then confirm with require_confirm: true. This guides the agent on the correct invocation sequence.

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