WAzion MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal detail. It does not clarify whether this is read-only (implied by 'get' but not stated), what specific status values are returned (connected, QR pending, disconnected), rate limits, or side effects.

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 appropriately brief and front-loaded with the purpose, but the trailing '[query]' artifact reduces clarity. Without this placeholder error, it would score higher for efficient structure.

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 the complexity of WhatsApp session management (multiple states, QR codes, connection health) and the absence of an output schema, the description is insufficient. It does not explain what constitutes 'status', what fields are returned, or how to interpret different session states.

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 has 100% description coverage for the single optional parameter (session_id). The description implies the parameter filters from 'all sessions' to a specific one, but adds no syntax details, examples, or format constraints beyond what the schema already provides. Baseline 3 is appropriate given complete schema coverage.

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 states the basic purpose (shows status of WhatsApp sessions) with a specific verb and resource, but includes a confusing '[query]' placeholder that appears to be an unfilled template variable. It fails to differentiate from siblings like 'get_whatsapp_connection_status' or 'get_whatsapp_health', leaving ambiguity about what specific 'status' this tool returns.

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 when-to-use guidance is provided. The description does not clarify when to query a specific session_id versus retrieving all sessions, nor does it mention prerequisites like requiring an active WhatsApp connection or how this differs from 'get_whatsapp_connection_status'.

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