WAzion MCP Server

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

The '[mutation]' tag and 'existing' qualifier disclose write behavior and resource constraints, but without annotations, the description should ideally cover idempotency, error handling (invalid IDs), and side effects on active conversations, which are absent.

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 two-clause structure is efficient and front-loaded. The bracketed '[mutation]' tag is slightly informal but does not significantly impair readability. No redundant filler text is present.

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 simple two-parameter toggle operation with no output schema, the description covers the essential operation but lacks information on return values, error states, or confirmation of success that would complete the agent's understanding.

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?

With 100% schema description coverage, the structured data already documents both parameters fully. The description adds minimal semantic value beyond mapping 'Activar/Pausar' to the boolean logic already described in the schema.

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 dual action (activate/pause) and target resource (existing WhatsApp workflow), distinguishing it from create/delete siblings. However, it does not explicitly differentiate from 'bulk_toggle_workflows' 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?

No guidance is provided on when to use this single-workflow toggle versus 'bulk_toggle_workflows' for mass operations, or versus 'update_whatsapp_workflow' for configuration changes. No prerequisites or error conditions are mentioned.

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