bulk_delete_workflows

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

With no annotations, the description fully discloses behavioral traits: it is a mutation requiring confirmation, describes the two-step API interaction (first call returns success=false with requires_confirmation=true), and warns that re-calling invalidates the confirmation token. It also states the need for the 'confirm' parameter to execute.

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 relatively long but every sentence serves a purpose. It is front-loaded with the purpose and then provides step-by-step instructions. It could be slightly more concise, but the structure effectively guides the agent through a complex flow.

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 destructive nature and the required confirmation flow, the description is comprehensive. It covers prerequisites (list workflows), user confirmation, the two-step API behavior, and the confirm parameter. It also references sibling tools appropriately. No output schema, but the return behavior is partially described.

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 100%, so baseline is 3. The description adds no new meaning beyond the schema: it repeats 'Array de IDs de workflows' and 'pasar true para confirmar', which are already in the input schema. No additional parameter details are provided.

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 tool's purpose: 'Eliminar workflows en lote — Elimina multiples workflows de WhatsApp a la vez.' It specifies batch deletion of WhatsApp workflows, differentiating from the sibling tool 'delete_whatsapp_workflow' for single deletion.

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 guidelines: it mandates using 'list_whatsapp_workflows' first to obtain workflows and confirming with the user exact IDs. It warns against deleting without explicit confirmation, outlines the confirmation flow, and instructs the agent not to call the tool again after the initial response.

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