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 disclosure burden. It omits critical behavioral details: how the query parameter interacts with other filters (phone, comment, agent_name), what the 'para merge' phone parameters actually do in a search context, pagination behavior, and return format.

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 extremely concise (single line) and front-loaded with the action. However, given the tool's complexity (9 parameters including confusing merge fields), this brevity becomes underspecification rather than efficient communication.

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?

With 9 parameters (including unexplained merge fields), no output schema, and no annotations, the description is inadequate. It fails to explain parameter relationships, search logic (AND/OR), or the significance of 'primary_phone' and 'secondary_phone' being labeled 'para merge'.

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 high (89%), establishing a baseline of 3. The description adds minimal value beyond the schema, only hinting at the required 'query' parameter via the '[query]' placeholder. It does not clarify the unusual merge-related parameters or how multiple filters combine.

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 core action (busca/search) and resource (comentarios/comments), including scope (todos los clientes/all customers). However, it fails to distinguish from sibling 'get_customer_comments' or explain why merge-related parameters (primary_phone, secondary_phone) exist in a search tool.

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 provided on when to use this tool versus 'get_customer_comments' or 'search_customers'. The '[query]' placeholder hints at the required parameter but provides no contextual guidance on filter combinations or search syntax.

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