zda_delete_ticket_form

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

With no annotations, the description correctly discloses the guarded (preview-then-confirm) behavior. However, it omits details like required permissions, what happens upon successful deletion, or side effects on related 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?

Two sentences, no extraneous words. The first sentence states purpose, the second explains the guarded pattern. Efficiently packs necessary information without filler.

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 has no output schema, so the description could mention return value (e.g., preview object or success confirmation). It also lacks context on error scenarios or prerequisites. Given the simple two-parameter schema, it reasonably covers the core behavior but misses minor details.

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 schema covers 50% of parameters (id described). The description adds meaning by explaining that require_confirm controls whether to preview or delete, and that calling without it shows what would be deleted. This compensates for the missing schema description.

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 ticket_form' with a specific verb and resource. The guarded pattern (preview before delete) distinguishes it from sibling delete tools that may not have such a mechanism.

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 steps: first call without require_confirm to preview, then with require_confirm: true to apply. It does not compare with sibling delete tools or state when not to use, but the two-step process is clearly explained.

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