cigchat_whatsapp_template_delete

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

With no annotations provided, the description carries the full burden and excels: it explicitly labels the operation DESTRUCTIVE and irreversible, discloses the confirmation flow requirement, and states the required authentication scope. This is exemplary transparency for a mutation tool.

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 deliver all essential info: action, endpoint, destructive warning, confirmation process, and scope requirement. No filler, perfectly front-loaded with the most important warning.

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?

Despite no output schema, the description covers the destructive nature, confirmation flow, and permission requirement, which are the main concerns for a delete tool. It does not describe the final success response, but the impact statement is mentioned, making it sufficiently complete for its complexity.

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 description adds critical meaning to the confirm parameter by explaining the two-step flow: first call omits it to receive an impact statement, then only pass the token after human approval. Although the schema already describes confirm well, the description reinforces the workflow and makes the parameter's purpose unambiguous.

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 the action: 'Delete Whatsapp template' with the exact endpoint. This specific verb+resource combination distinguishes it from sibling tools like cigchat_whatsapp_template_create, list, and sync.

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 gives explicit step-by-step guidance: call once without confirm to get an impact statement, then pass the token after approval. It also notes the required 'Manage Flow' scope. No alternatives are mentioned, but none exist for deletion.

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