WAzion MCP Server

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

With no annotations provided, the description carries the full burden but discloses minimal behavioral traits. It does not clarify the read-only nature, return format, pagination behavior, or what the trailing '[query]' artifact signifies. It simply states the tool 'shows' questions without explaining side effects or limits.

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 compact and front-loaded, consisting of a single sentence. However, the presence of the unexplained '[query]' placeholder at the end creates confusion and reduces clarity, preventing a higher score.

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 4 parameters with 50% schema coverage and no output schema, the description is insufficient. It fails to explain return values, parameter dependencies (hours vs period), or filtering capabilities implied by the '[query]' artifact, leaving significant gaps for an agent attempting invocation.

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 coverage is 50% (hours and limit lack descriptions). While the description mentions 'recent' questions, it does not explicitly document the `hours` parameter, explain the `limit` parameter, or clarify how `hours` and `period` interact as alternative time-window mechanisms.

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 retrieves recent questions ("Muestra las ultimas preguntas") from the Product Q&A plugin, providing specific verb and resource. However, it does not differentiate from siblings like `get_product_qa_questions` or `get_unanswered_plugin_questions` beyond implying a time-based scope.

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 provides no guidance on when to use this tool versus related alternatives such as `get_product_qa_questions` or `get_plugin_conversations`. It lacks explicit prerequisites, exclusions, or contextual triggers for selection.

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