waha_list_sessions

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether stopped sessions are returned by default (only implied via the parameter), whether the call requires an authenticated/running server, or what ordering/scope the listing has. The mutation-free nature of a list operation can be inferred, but little else.

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 short sentences with the purpose front-loaded and the parameter note second; no wasted clauses. It is tight, though the second sentence could have been folded into a fuller usage statement rather than standing alone as a bare default note.

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?

With an output schema present, return values need not be described, and there is only one optional parameter, so the bar is low and the description mostly meets it. For a read tool with zero annotations, however, it omits any environment/auth assumptions an agent might need before calling.

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%, so the description must compensate, and it does explain include_stopped as the switch that surfaces stopped sessions, implying the default excludes them. That covers the sole parameter adequately but adds no detail on how 'stopped' is defined or whether the flag changes the response shape.

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?

"List WhatsApp sessions" states a specific verb and resource, clearly distinguishable from waha_get_session (single session) and waha_status by naming the collection being enumerated. It does not explicitly call out siblings, but the verb+resource combination is unambiguous.

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 offers no guidance on when to use this list tool versus waha_get_session, waha_status, or waha_list_chats; the second sentence is parameter semantics rather than usage context. An agent must infer the selection criteria from tool names alone.

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