disconnect_whatsapp

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

No annotations are provided, so the description carries the full burden. It discloses the mutation nature, deletion of auth data, and the need for confirmation. It could mention reversibility or side effects but is reasonably transparent.

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 concise with two sentences and a note, front-loading the purpose. Every sentence contributes necessary information 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?

Given no annotations or output schema, the description covers purpose, parameter conditions, and confirmation. It references a related tool for IDs. It does not describe success/failure responses but is sufficient for a simple mutation.

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%. The description adds context: session_id required when multiple numbers, references get_whatsapp_status for IDs, and labels confirm as required confirmation for a dangerous action. This adds value beyond the schema.

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 disconnects a WhatsApp session and deletes authentication data. It uses a specific verb ('Desconectar') and resource ('WhatsApp'), and distinguishes from siblings like connect_whatsapp and reconnect_whatsapp.

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 guidance: requires session_id if multiple numbers, and requires confirm=true for execution. However, it does not explicitly specify when to use this tool versus alternatives like delete_whatsapp_session or precheck_delete_whatsapp_session.

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