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 of behavioral disclosure. While 'Ver' (View) implies read-only access, the description lacks critical details: pagination behavior, data retention limits, rate limiting, or what constitutes 'execution' statistics specifically.

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 brief (one sentence with an em-dash), but the trailing '[query]' appears to be a template artifact or placeholder that creates confusion and wastes space. This artifact detracts from an otherwise efficient structure.

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?

Given zero annotations and no output schema, the description should provide behavioral context or return value hints. For a statistics retrieval tool with simple parameters, the description is minimally adequate but leaves significant gaps regarding output format, error conditions, and data scope.

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 (both 'days' and 'session_id' are well-documented in the schema), the baseline is 3. The description mentions 'en un periodo' which loosely maps to the days parameter but adds no syntax details, validation rules, or examples 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 shows execution statistics ('estadísticas de ejecución') of WhatsApp workflows over a time period ('en un periodo'). However, it fails to distinguish from similar siblings like get_whatsapp_workflow_stats and get_whatsapp_workflow_logs, leaving ambiguity about which specific type of data this returns.

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_whatsapp_workflow_stats or get_whatsapp_workflow_logs. No mention of prerequisites (e.g., whether session_id is required vs optional) or when this query is preferable to other analytics tools.

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