WAzion MCP Server

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

No annotations provided, so description carries full burden. The [mutation] tag explicitly indicates this is a write operation, which is valuable disclosure. However, it lacks details on side effects, idempotency, what constitutes a 'detected conversation,' or whether existing lists with the same name are overwritten or appended.

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?

Two-part Spanish structure with em-dash is slightly redundant ('Crear lista... — Crea una lista...'), but efficiently conveys the essential information in minimal space. No unnecessary fluff, though the [mutation] tag is somewhat technical for a description field.

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?

Adequate for a 2-parameter creation tool with no output schema. However, it fails to explain what 'Smart Follow-up' detection means or what data actually gets imported into the list (contact info, conversation IDs, etc.), leaving operational ambiguity despite the clear intent.

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 description coverage is 100% (both name and period fully documented in schema). The description doesn't add syntax details or parameter interaction logic, but the schema is self-sufficient. Baseline score appropriate for high 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?

Description provides specific verb (Crea/creates), resource (lista de contactos/contact list), and distinguishing scope (desde conversaciones detectadas por Smart Follow-up/from conversations detected by Smart Follow-up). This clearly differentiates it from sibling tools like create_contact_list (generic) and create_list_from_inactive (different source criteria).

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?

Description states what the tool does but provides no guidance on when to use it versus alternatives like create_contact_list or create_list_from_inactive. No mention of prerequisites (e.g., Smart Follow-up being enabled) or exclusion criteria.

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