toggle_whatsapp_workflow

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

Annotations are absent, so the description carries full responsibility for behavioral disclosure. It notes [mutation] but does not detail side effects (e.g., what happens to running workflows), required permissions, or error conditions. The description is overly minimal.

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 extremely concise with two clear phrases and no redundant words. However, it could include more information without becoming verbose.

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 no annotations, no output schema, and only two parameters, the description is insufficient. It fails to explain what happens upon success/failure, whether the change is immediate, or if there are constraints (e.g., cannot pause a paused workflow).

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 input schema already provides descriptions for both parameters (id and enabled) with 100% coverage. The description adds no additional semantic meaning beyond what the schema conveys, so baseline 3 is appropriate.

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 (activate/pause) and the resource (WhatsApp workflow). The [mutation] tag reinforces that it modifies state. It is sufficiently distinct from siblings like create_whatsapp_workflow or update_whatsapp_workflow.

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 no guidance on when to use this tool versus alternatives (e.g., update_whatsapp_workflow). It does not mention prerequisites, such as the workflow must exist, nor does it indicate that this is the right tool for toggling enabled state.

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