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 explicitly signals write behavior, and the description clarifies that null removes the label (implied by context). However, it lacks disclosure on idempotency, return values, or side effects beyond the label update itself.

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 with zero waste. Front-loaded with action ('Editar sesion...'), immediately followed by scope clarification and practical examples. The '[mutation]' tag is appropriately placed at the end. Every word earns its place.

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 2-parameter update tool with 100% schema coverage and no output schema, the description is complete. It covers the operation, use case, and examples. Could improve by mentioning the operation's idempotency or success behavior, but adequate for the complexity level.

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 has 100% description coverage (baseline 3). The description adds semantic value by providing concrete example label values ('Soporte', 'Ventas') that clarify the expected input format and organizational use case, going beyond the schema's technical description.

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?

Specific verb ('Actualiza') + resource ('sesion de WhatsApp conectada') with clear scope (etiqueta/nombre). Distinguishes from siblings like connect_whatsapp, delete_whatsapp_session, and update_whatsapp_profile by specifying it modifies the session's label for identification purposes.

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?

Provides implied usage context through the use case ('Util para identificar numeros') and practical examples ('Soporte', 'Ventas'), but lacks explicit guidance on when to use this versus update_whatsapp_profile or workflow tools, and does not mention prerequisites beyond the schema reference.

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