WAzion MCP Server

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

No annotations provided, so description carries full burden. It discloses the QR code return mechanism and includes '[mutation]' tag indicating write operation, but omits session lifecycle details, timeout behavior, or error states after QR generation.

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?

Three efficient components: hyphenated title phrase, process description, and mutation tag. No redundant words; 'Conectar número de WhatsApp' front-loads the action while subsequent sentences add specific behavioral details about the QR output.

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?

Adequately covers the essential output (QR code) given no output schema exists, and references both parameters. Could improve by mentioning QR expiration time, connection timeout windows, or session limits that might affect the connection process.

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 (label max 50 chars, force_new behavior), establishing baseline 3. Description adds value by contextualizing parameters within the connection initiation flow but does not add syntax or format details beyond 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?

Description clearly states it initiates connection for a new WhatsApp number ('Inicia el proceso de conexión de un nuevo número') and distinguishes from siblings like reconnect_whatsapp through the 'nuevo' specifier. Specific verb+resource combination makes intent unambiguous.

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?

Implies usage by mentioning QR code scanning requirement ('Devuelve un código QR para escanear'), suggesting a phone must be available. However, lacks explicit guidance on when to use this versus reconnect_whatsapp or prerequisites like existing session limits.

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