waha_logout_session

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 mentions that the session is kept but the WhatsApp account is disconnected, which is useful behavioral context. However, it lacks details on permissions required, whether this is reversible, what happens to pending messages, or error conditions, which are important for a mutation tool.

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 a single, efficient sentence that front-loads the core action and adds clarifying context without unnecessary words. Every part of the sentence earns its place by distinguishing the tool's behavior.

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 mutation tool with no annotations and no output schema, the description is minimally adequate. It explains the core action and a key behavioral trait (keeps session), but lacks details on side effects, error handling, or return values, leaving gaps in understanding the tool's full impact.

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 description coverage is 100%, with the single parameter 'session' documented as 'Session name' with a default value. The description doesn't add any parameter-specific information beyond what the schema provides, so the baseline score of 3 is appropriate.

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 action ('Logout from a WhatsApp session') and specifies the resource ('WhatsApp session'), distinguishing it from sibling tools like waha_stop_session or waha_delete_session by clarifying it 'keeps session but disconnects WhatsApp account'.

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 implies usage context by stating it 'keeps session but disconnects WhatsApp account', suggesting it's for temporarily disconnecting while preserving session data. However, it doesn't explicitly state when to use this versus alternatives like waha_stop_session or waha_delete_session, nor does it mention prerequisites like needing an active session.

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