waha_start_session

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

With no annotations, the description carries full behavioral burden. It usefully discloses that QR-code scanning via the dashboard is required, but it does not explain permissions, side effects, what happens if the session is already running, or how the start operation behaves.

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, front-loaded with the core action and followed by the key operational detail. There is no wasted text.

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. However, for a lifecycle mutation tool with no annotations and an undocumented required parameter, the description should do more to cover prerequisites and state behavior.

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?

There is one required parameter, 'session', with 0% schema description coverage. The description refers to 'its QR code' but does not explain that 'session' is the session identifier/name or how to obtain it, so the parameter semantics remain under-specified.

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: start a stopped WhatsApp session. It is clear what the tool does and implicitly distinguishes itself from create_session by requiring an already stopped session, though it does not name siblings explicitly.

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 phrase 'stopped WhatsApp session' gives implied usage context: use this for existing stopped sessions rather than new ones. However, it does not explicitly say when to use waha_create_session or waha_stop_session instead, nor does it state prerequisites or failure conditions.

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