zda_delete_group

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

With no annotations, the description carries full burden. It discloses the guarded (two-step) pattern, explaining that the first call is a preview and the second is destructive. This is key behavioral information. However, it omits side effects, permissions, or what happens if the group has dependencies.

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 with no fluff. First sentence states the action, second explains the guarded usage pattern. Front-loaded with essential information.

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?

Given the tool's simplicity (delete with preview), the description covers the main usage flow. However, it lacks details on what the preview returns (likely the group object) and error conditions. For a guarded tool, knowing the preview output is valuable. Still, it is mostly 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 coverage is 50% (only id described). The description fully explains both parameters: 'id' implicitly identifies the group, and 'require_confirm' is described in the guarded pattern as the flag to switch from preview to apply. This compensates for the missing schema description of require_confirm.

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 group', which is a specific verb and resource. It distinguishes from sibling tools like create, update, get, and list by specifying delete. The guarded preview pattern adds nuance.

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 usage guidance: call without require_confirm to preview, then with require_confirm: true to apply. This tells the agent when to use each mode. However, it does not exclude other approaches (e.g., deactivation) or compare to other delete tools for different objects.

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