zda_delete_sla_policy

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

With no annotations provided, the description carries the full burden of behavioral transparency. It explains the guard mechanism (preview vs actual delete), which is a key behavioral trait. However, it does not disclose what the preview returns, what happens on successful deletion, or potential error conditions.

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 two sentences: first states the purpose, second explains the guarded usage. Both sentences are essential and there is no verbose or redundant content. It is front-loaded and concise.

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 two parameters and no output schema. The description covers purpose and guard mechanism, but it does not explain return values (e.g., what the preview returns, what a successful delete returns) or error behavior (e.g., invalid id). For a delete operation, this is adequate but not fully complete.

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 description coverage is 50%: only 'id' has a description ('Numeric object ID'). The description compensates for 'require_confirm' by explaining its role in the guarded workflow (preview vs apply). This adds semantic meaning beyond the schema.

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 sla_policy', specifying the verb (delete) and resource (sla_policy). This distinguishes it from sibling tools like create, update, and get for SLA policies.

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 guidance on the guarded two-step process: first call without require_confirm to preview, then re-call with require_confirm: true to apply. This tells the agent how to use the tool safely, though it doesn't explicitly state when not to use it or list alternatives.

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