WAzion MCP Server

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

No annotations provided, so description carries full burden. It includes '[mutation]' tag and explains the confirmation requirement, indicating destructive/safety-critical behavior. However, it fails to describe the outcome of cancellation (deleted, status-changed, recoverable?) or side effects.

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?

Efficiently structured with title-like front-loading ('Cancelar mensaje programado'), em-dash separation, and parenthetical safety note. Every element earns its place; zero wasted words while conveying domain, action, mutation type, and safety protocol.

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 3 parameters with full schema coverage and no output schema, description adequately covers the tool's scope (WhatsApp domain), purpose, and critical safety constraint. Distinguishes from email cancellation siblings. Could improve by describing success/failure behavior or cancellation state outcomes.

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 has 100% description coverage, establishing baseline 3. Description adds valuable semantic context for the 'confirm' parameter, explaining it as a safety confirmation required to execute the 'peligrosa' (dangerous) action, which aids agent reasoning about when/why to set it.

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?

Description clearly states the action (Cancelar/Cancels) and specific resource (mensaje de WhatsApp programado/scheduled WhatsApp message). Explicitly mentioning 'WhatsApp' effectively distinguishes it from sibling tool cancel_scheduled_email.

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 explicit usage guidance for the confirmation safety pattern ('requiere confirmación: pasar confirm=true para ejecutar'). Lacks explicit contrast with related siblings like update_scheduled_message or create_scheduled_message, though the distinction is somewhat implicit.

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