reconnect_whatsapp

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

Discloses that manual QR scanning may be required, which is a behavioral trait beyond the schema. The [mutation] tag also indicates state change. No annotations are provided, so description partially fills the gap.

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?

Two concise sentences with a mutation tag. No wasted words; critical information is front-loaded.

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 simple tool with one optional parameter and no output schema, the description covers purpose, condition, and behavioral hints. Could mention expected result (e.g., success status) but adequate.

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?

The schema covers 100% of parameters, and the description adds context: session_id is required when multiple numbers exist, and references get_whatsapp_status to obtain IDs.

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 reconnects an existing WhatsApp session, distinguishing it from sibling tools like connect_whatsapp and disconnect_whatsapp. It adds specifics about QR scanning and session_id requirement when multiple numbers exist.

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?

Describes when to use (to reconnect an existing session) and conditionally requires session_id. However, it does not explicitly exclude initial connection or reference alternative tools like connect_whatsapp.

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