WAzion MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions obtaining 'all' lists, hinting at pagination needs, but fails to disclose read-only safety, rate limits, return format, or pagination limits. The '[query]' placeholder appears to be a template error rather than meaningful 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?

While brief and front-loaded, the description contains a malformed artifact '[query]' at the end that appears to be an unsubstituted template variable. This creates confusion and reduces clarity rather than adding value.

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 2-parameter list operation with no output schema, the description minimally suffices by indicating it returns all contact lists. However, given the lack of output schema, it should ideally describe the return structure or list format, which it does not provide.

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% ('Numero de pagina', 'Texto de busqueda'), establishing baseline 3. The description implies the scope is 'all' lists, giving implicit context for the page parameter, but does not explicitly explain the search parameter syntax or pagination behavior beyond the schema definitions.

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 tool lists/obtains contact lists and specifies the domain (mass marketing). The use of 'todas' (all) distinguishes it from sibling get_contact_list_detail which likely retrieves a single list. However, it doesn't explicitly differentiate from other list operations like list_blacklist.

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 versus get_contact_list_detail or when to apply the search parameter versus retrieving all results. The description implies general usage but lacks 'when-not' conditions or alternative recommendations.

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