WAzion MCP Server

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

No annotations provided, so description carries full burden. The '[mutation]' tag indicates this is a write operation with side effects, which is helpful. However, it lacks disclosure of idempotency, reversibility (can the created workflow be deleted?), whether the workflow is active immediately, or what happens if the template_id is invalid.

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?

Efficient two-part structure with a Spanish title phrase and explanatory sentence. The '[mutation]' tag is concise and informative. No redundant or wasted words, though the em-dash formatting slightly splits attention.

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?

For a mutation tool with 3 parameters and no output schema, the description meets minimum viability by stating the core operation. However, given the complexity of workflow creation and the presence of similar siblings, it should explain the output (e.g., returns workflow ID), error scenarios, or at least reference related tools to aid selection.

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 100%, so all parameters (template_id, session_id, name) are documented in the schema itself. The description adds no additional semantic context beyond what's in the schema (e.g., no naming conventions, no explanation of session_id's relationship to the workflow, no default behaviors for optional fields).

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 creates a new WhatsApp workflow from an existing template (specific verb + resource + source). However, it loses one point because it doesn't differentiate from the sibling `create_whatsapp_workflow` (which likely creates from scratch), and there's a confusing directional mismatch between the tool name (suggests 'template from workflow') and description (states 'workflow from template').

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?

No explicit guidance on when to use this tool versus `create_whatsapp_workflow` or `save_as_whatsapp_template`. No prerequisites mentioned (e.g., that the template must exist first), and no indication of when this approach is preferred over building a workflow manually.

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