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. It mentions filtering by deadline status (passed) and task status (pending), but fails to disclose pagination behavior, how the 11 filter parameters interact (AND/OR logic), or what happens when no results are found. The trailing '[query]' is confusing and unexplained.

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 appropriately brief and front-loaded with the key concept ('Tareas vencidas'). However, the trailing '[query]' appears to be a placeholder or editing artifact that wastes space without adding meaning, slightly detracting 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 11 optional filter parameters including pagination controls and multiple ID fields, the description is insufficient. It fails to indicate the rich filtering capabilities available or provide guidance on typical query patterns, leaving significant gaps despite the lack of output schema.

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 schema adequately documents all 11 parameters. The description does not add parameter-specific semantics beyond the vague '[query]' reference, meeting the baseline expectation when schema coverage is comprehensive.

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 overdue tasks (tareas vencidas), specifically those pending with past deadlines. It uses a specific verb-resource combination ('Muestra... tareas pendientes') and implicitly distinguishes from siblings like list_tasks by focusing exclusively on overdue items.

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 tool versus alternatives like list_tasks or get_agent_tasks. No mention of prerequisites or exclusion criteria. The user must infer from the name and description that this is specifically for overdue task retrieval.

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