WAzion MCP Server

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

No annotations are provided, and the description fails to disclose critical behavioral traits such as read-only safety, what happens when a phone number has no conversations, rate limits, or the structure of returned file metadata.

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?

Brief single-sentence structure is efficient, but the trailing '[query]' appears to be a template artifact that wastes space and creates confusion. Information is front-loaded but not perfectly clean.

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 3-parameter tool with no output schema and no annotations, the description is insufficient. It lacks explanation of return values, pagination behavior, and relationship to file management siblings (download/delete).

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 coverage is 67% (limit lacks description). The description implicitly references the phone parameter via 'con un cliente' but does not explicitly map parameters, explain pagination mechanics, or compensate for the missing limit documentation.

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?

Uses specific verb 'Lista' (Lists) and resource 'archivos' (files) to describe listing shared files in a client conversation. However, it includes a confusing '[query]' artifact and does not explicitly differentiate from siblings like download_conversation_file or delete_conversation_file.

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 no guidance on when to use this tool versus alternatives (e.g., when to list vs. download), nor does it mention prerequisites like needing a valid phone number or how to handle pagination scenarios.

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