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 disclosure burden. It adds the [mutation] classification and 'acción peligrosa' warning with confirmation requirements, but lacks details on reversibility (whether a new picture can be uploaded later), side effects on active conversations, or what displays after removal.

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 the action front-loaded ('Eliminar foto de perfil de WhatsApp'), followed by the detailed explanation and critical confirmation instruction. No redundant or wasted text; every element serves selection or invocation clarity.

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?

Adequately complete for a focused 2-parameter destructive operation. It covers the mutation nature and safety confirmation. With no output schema present, the description appropriately focuses on input requirements, though it could briefly mention the resulting state (e.g., default avatar display).

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 description coverage is 100%, with both session_id and confirm well-documented in the schema. The description reinforces the confirm parameter's purpose in the main text ('requiere confirmación'), providing helpful redundancy but not substantial additional semantic information beyond the schema definitions.

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 specific action (eliminar/removes) and resource (foto de perfil de WhatsApp/profile picture of a WhatsApp session). It effectively distinguishes from siblings like update_whatsapp_profile (which modifies fields) and delete_whatsapp_session (which removes the entire session) through precise naming and 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?

Provides explicit guidance on the confirmation requirement ('requiere confirmación: pasar confirm=true para ejecutar'), which is critical for invocation. However, it does not explicitly contrast this tool with alternatives like update_whatsapp_profile for changing pictures versus removing them entirely.

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