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. It includes a helpful '[mutation]' tag indicating a write operation, but lacks disclosure of side effects such as duplicate handling, idempotency, validation rules for phone numbers, or what occurs if the list_id doesn't exist.

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 compact with two components separated by an em-dash. It efficiently conveys the operation in Spanish without filler text, though the initial infinitive phrase slightly duplicates the subsequent conjugated verb statement.

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 two-parameter mutation tool without output schema, the description adequately explains the core operation. However, it could improve by mentioning success indicators, error conditions, or whether existing contacts in the target list are updated or skipped.

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?

Input schema has 100% description coverage (list_id and phones are documented). The description adds no additional parameter semantics (e.g., phone number format, array size limits), but with high schema coverage, baseline 3 is appropriate.

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 the action (imports), resource (contacts), source (WhatsApp conversations), and destination (marketing list). It distinguishes from siblings like `import_contacts_from_crm` by specifying the WhatsApp conversation source, and hints at differentiation from `import_contacts_from_all_conversations` via 'seleccionados' (selected), though this could be more explicit.

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 guidance on when to use this tool versus alternatives like `import_contacts_from_all_conversations` or `add_contacts_to_list`. It does not mention prerequisites (e.g., existing conversations) or exclusion criteria.

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