Terminate all active WhatsApp Web sessions to stop messaging operations and clear resources.
[Session] Terminate all sessions. Terminates all sessions.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "session_terminateAll"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description carries the full burden of behavioral disclosure. It only states the action ('terminate all sessions') without explaining consequences, reversibility, impact on the current session, or any required authentication/permissions. This is a destructive operation with zero safety context.
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 extremely brief but redundant: 'Terminate all sessions. Terminate all sessions.' The second sentence adds no value. It is under-specified rather than genuinely concise, failing to use the available space to convey useful context.
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?
The tool is a destructive, terminal action with several closely related siblings (session_terminate, session_terminateInactive). The description provides no distinction between these, no side effects, and no scope clarification. For a tool of this complexity, the description is insufficiently 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 tool has zero parameters, so the schema is trivially covered and the description adds no parameter-specific meaning. Per rubric, 0 params receive a baseline score of 4.
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 terminates all sessions, with a specific verb and resource. However, it is essentially a restatement of the tool name and does not distinguish itself from sibling tools like session_terminate or session_terminateInactive.
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?
No guidance is provided on when to use this tool versus the many related session tools. There is no mention of alternatives, prerequisites, or situations where this tool should be avoided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.