waha_restart_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 of behavioral disclosure. It states the action ('Restart') but doesn't explain what restarting entails—whether it preserves session data, requires re-authentication, interrupts ongoing operations, or has side effects. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 with zero wasted words. It's front-loaded with the core action ('Restart a WhatsApp session'), making it immediately clear and easy to parse.

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?

Given the complexity of restarting a session (a mutation operation with potential side effects), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, outcomes, error conditions, or dependencies, leaving the agent with insufficient context to use the tool effectively beyond its basic purpose.

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 input schema has 1 parameter with 100% description coverage ('session' with description 'Session name'), so the schema fully documents the parameter. The description adds no additional parameter semantics, but with high schema coverage and only one parameter, a baseline of 4 is appropriate as the description doesn't need to compensate for gaps.

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 verb ('Restart') and resource ('a WhatsApp session'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'waha_start_session' and 'waha_stop_session' by specifying the restart action, though it doesn't explicitly contrast with them in the description text itself.

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 provides no guidance on when to use this tool versus alternatives like 'waha_start_session' or 'waha_stop_session'. It doesn't mention prerequisites (e.g., whether a session must exist or be in a specific state) or typical use cases (e.g., recovering from errors, refreshing connections).

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