whatsapp_disconnect

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

With no annotations, the description warns that the tool is destructive and requires confirmation. This provides key behavioral context, though it could mention the post-logout state or reversibility.

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 clear sentences: the purpose and a warning with usage instruction. No unnecessary information.

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 the tool's simplicity and the presence of an output schema, the description covers purpose, destructive nature, and parameter requirement. It could mention the need for an active connection, but it is largely complete.

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 description adds significant meaning to the 'confirmed' parameter beyond the schema, explicitly stating it must be set to True and that the user must be asked first.

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 'Logout from WhatsApp' using a specific verb and resource, and it distinguishes itself from siblings like 'whatsapp_reset_session' by focusing on disconnection.

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 usage guidance: it is destructive and requires confirmed=True, and instructs to always ask the user first. However, it does not explicitly compare to alternatives like reset_session.

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