delete_whatsapp_session

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

With no annotations, the description carries the full burden. It identifies the operation as a mutation via '[mutation]' and requires confirmation ('confirm=true'). It does not explicitly state irreversibility or data implications, but the migration parameter is described in the schema.

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 very concise: two sentences plus a mutation label and confirmation requirement. It is front-loaded with the main action and condition, with no wasted words.

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 delete operation with 3 parameters and no output schema, the description covers the essential behavioral traits (precondition, mutation, confirmation). It could mention the sibling precheck tool for completeness, but it is sufficient for safe invocation.

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 coverage is 100% with parameter descriptions. The main description adds value by stating the precondition for session_id (must be disconnected), which is not in the schema. This extra context helps the agent select the correct session.

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 'Elimina una sesion de WhatsApp desconectada' (deletes a disconnected WhatsApp session), specifying the resource and action. It distinguishes from siblings by noting it only works with disconnected sessions, making the purpose unambiguous.

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?

The description provides a clear precondition: 'Solo funciona con sesiones en estado disconnected'. However, it does not explicitly mention when not to use this tool or suggest alternatives like the sibling 'precheck_delete_whatsapp_session' for verification.

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