waha_stop_session

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

With no annotations, the description carries the full burden. It usefully discloses one key behavioral trait: stopping does not delete session data. It does not describe permissions, whether the stop is reversible, or what happens to connected clients, leaving meaningful gaps for a lifecycle 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?

A single compact sentence with the action front-loaded and the important non-destructive scope stated immediately. No filler.

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?

An output schema exists, so return values need not be explained. For a one-parameter lifecycle tool this is reasonably complete on purpose, but it omits parameter meaning and operational side effects, which are still relevant with no annotations.

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 0%, and the description never mentions the sole 'session' parameter. The parameter name is self-explanatory enough to infer, but the description adds no format, source, or example guidance beyond the bare schema property.

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 states a specific verb and resource: 'Stop a running WhatsApp session.' It also clarifies scope with 'without deleting its data,' distinguishing the operation from deletion. It does not explicitly compare against siblings like waha_start_session, but the purpose is clear.

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?

Usage is implied by 'running' — use it on an active session — and the data-preservation note suggests caution around destructive alternatives. However, it never explicitly says when to use this tool versus waha_start_session or other lifecycle tools, nor does it state prerequisites.

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