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 disclosure burden but fails to specify read-only safety, return format, pagination behavior, or what 'available' means in this context. The '[query]' suffix ambiguously suggests filtering capabilities without confirming whether the tool accepts query parameters.

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 brief at one sentence, but the structure is compromised by the em-dash separation and the '[query]' placeholder that appears to be a template remnant. The front-loading is adequate but the artifact distracts from the core message.

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 absence of an output schema and the presence of numerous session-related siblings (assign, delete, list scheduled), the description should explain the specific nature of 'marketing sessions' and what data is returned. It fails to provide this necessary context for proper tool 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?

While the input schema contains zero parameters (baseline 4), the description's inclusion of '[query]' at the end introduces confusion by implying query functionality that the schema does not support. This unnecessary artifact reduces clarity rather than adding semantic value.

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 tool obtains WhatsApp sessions for campaign sending ('Obtiene las sesiones de WhatsApp disponibles para envío de campañas'), providing a specific verb and resource. However, it suffers from mixed formatting ('Ver sesiones de marketing' vs the longer Spanish description) and contains a dangling '[query]' artifact that suggests unfinished templating.

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 is provided on when to use this tool versus siblings like 'assign_marketing_session', 'list_whatsapp_scheduled_sessions', or 'delete_whatsapp_session'. The description does not clarify what constitutes a 'marketing session' compared to other session types available in the extensive sibling list.

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