WAzion MCP Server

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

No annotations are provided, so the description carries the full burden. While it includes the '[mutation]' tag indicating a write operation, it lacks disclosure about duplicate handling, validation behavior, idempotency, or the file upload workflow required for the `tmp_id` parameter. For a destructive import operation, this is insufficient behavioral context.

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 with two sentences plus the mutation tag. The opening 'Importar contactos de marketing — Importa contactos...' is slightly redundant (repeating the verb), but overall the structure is front-loaded and efficient.

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 tool's complexity (7 parameters, 4 distinct import modes including file-based imports), the description is incomplete. It fails to mention the CSV/TXT import modes visible in the schema, does not explain the `tmp_id` file upload prerequisite, and provides no output schema or return value information.

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, documenting all 7 parameters including the enum values for `source`. The description mentions manual entry and conversations ('Soporta entrada manual...o importacion desde conversaciones') but omits the CSV/TXT file modes evident in the schema, adding minimal semantic value beyond the structured 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?

The description clearly states it imports contacts to a mass marketing list ('Importa contactos a una lista de marketing masivo') and mentions manual entry and conversation import sources. However, it does not clearly differentiate from siblings like `import_contacts_manual`, `add_contacts_to_list`, or `import_contacts_from_conversations`, which appear to offer similar functionality.

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 on when to use this tool versus the numerous sibling import tools (e.g., `import_contacts_from_crm`, `import_contacts_manual`). No mention of prerequisites like file uploads for CSV mode or when to prefer `add_contacts_to_list` instead.

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