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 successfully identifies this as a mutation and emphasizes the confirmation requirement ('requiere confirmación'). However, it lacks details on side effects, reversibility of actions, or what happens when different actions are performed beyond the confirmation flow reference.

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 generally efficient but contains redundancy: it mentions the confirmation requirement twice ('Esta accion requiere confirmacion' and 'requiere confirmación: pasar confirm=true'). The [mutation] tag is useful metadata but the repetition could be consolidated.

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 this is a 6-parameter mutation tool with no output schema and 7 different action types (including complex ones like resolve_conflict and keep_both), the description provides minimum viable coverage. It addresses the confirmation safety requirement but lacks detail on return values, error states, or behavioral differences between the action types.

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?

While the schema has 100% description coverage (baseline 3), the description adds valuable behavioral context for the confirm parameter by explicitly stating it is required for this dangerous action ('pasar confirm=true para ejecutar'). This links the parameter to the confirmation flow safety mechanism beyond what the schema describes.

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 manages knowledge snippets and lists specific actions (approve, reject, edit, delete). However, it fails to distinguish this unified tool from specific sibling tools like approve_knowledge_snippet, reject_knowledge_snippet, delete_knowledge_snippet, edit_knowledge_snippet, resolve_knowledge_conflict, and keep_both_knowledge_snippets that appear to perform the same individual actions.

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?

Provides useful workflow guidance by mentioning to use filter=pending with list_knowledge_snippets to find pending reviews. However, it completely lacks guidance on when to use this unified tool versus the individual sibling action tools (approve_knowledge_snippet, reject_knowledge_snippet, etc.), which is critical given the overlapping functionality.

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