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 discloses the mutation aspect via '[mutation]' tag and identifies the target as 'marketing masivo', but omits critical behavioral details like duplicate handling, phone validation rules, batch size limits, or partial failure behavior.

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 efficiently contained in one sentence with an em-dash structure. While the leading phrase 'Importar contactos manualmente' partially restates the tool name, the remainder packs specific resource and method details without waste.

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 import tool with no output schema, the description covers the essential operation and target resource. However, given this is a mutation operation with no annotations, it should mention side effects like duplicate handling or validation requirements to be fully complete.

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?

With 100% schema description coverage, the baseline is 3. The description adds semantic context by mentioning 'lista de marketing masivo' (list_id) and 'escribiendo los telefonos' (phones), but doesn't add syntax details, example formats, or constraints beyond what the schema already provides.

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 by manually writing phone numbers. The phrase 'escribiendo los telefonos manualmente' effectively distinguishes this from sibling import tools (like import_contacts_from_crm or import_contacts_from_platform) that pull from automated sources, though it doesn't explicitly name them.

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?

The description implies usage context through 'manualmente' (suggesting use this for manual entry vs automated imports), but lacks explicit when-to-use guidance or named alternatives. It doesn't clarify when to choose this over add_contacts_to_list or import_marketing_contacts.

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