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 and effectively discloses: (1) the mutation nature tagged as [mutation], (2) the state constraint preventing accidental deletion of active sessions, and (3) the danger level requiring explicit confirmation ('acción peligrosa'). It could further clarify what data is at risk if migrate_to is not used.

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 optimally concise with zero waste: a title fragment, the core action, the critical state constraint, the mutation tag, and the safety confirmation requirement—each sentence serving a distinct purpose for agent decision-making.

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?

For a destructive operation with data migration implications (migrate_to parameter), the description adequately covers safety protocols and constraints. Without an output schema, it appropriately focuses on input requirements and preconditions rather than return values.

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 input schema has 100% description coverage (baseline 3), the description adds valuable safety context beyond the schema by emphasizing the confirmation requirement in the main text and clarifying the operational constraint (disconnected state) that affects how session_id should be selected.

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 explicitly states the tool deletes a WhatsApp session ('Elimina una sesion de WhatsApp') and specifically clarifies it only works on disconnected sessions ('Solo funciona con sesiones en estado disconnected'), distinguishing it from sibling tools like disconnect_whatsapp or update_whatsapp_session.

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?

It provides clear constraints on when to use (only for 'disconnected' status) and explicitly notes the confirmation requirement. However, it misses the opportunity to mention the sibling tool precheck_delete_whatsapp_session as a prerequisite step or alternative for validation.

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