Restart Gateway Daemon

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

The description adds valuable context beyond annotations: 'it affects every agent on the host' and 'Brief downtime (~10s).' Annotations already signal destructive and non-read-only, but the specific scope and duration are new behavioral disclosures. It also highlights the version-specific limitation (OpenClaw 2.0), which helps set expectations.

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 composed of three short sentences, each carrying necessary information: the action, the trigger conditions, and the global impact/downtime. There is no fluff, but it could be slightly tightened; however, each sentence earns its place.

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?

For a tool with a single optional parameter and no output schema, the description adequately covers the purpose, when to use it, impact scope, and downtime. It doesn't explicitly mention how to confirm the restart succeeded (e.g., via clawops_status), but that is a minor omission for such a simple restart operation.

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 already provides a full description of stackName, including the default-stack behavior when omitted. The tool description does not add any extra meaning to the parameter, so the baseline 3 for high schema coverage applies.

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 opens with a specific verb and resource: 'Restart the OpenClaw gateway daemon on the remote instance.' This clearly distinguishes it from sibling tools like clawops_up or clawops_apply, which are about deployment/configuration rather than restarting. The 'Use when' clause further reinforces the intended purpose.

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?

It provides explicit trigger conditions: 'gateway-wide config change requires reload' or 'gateway is reported as unresponsive.' It also notes that per-agent restart is unavailable, ruling out that alternative. However, it doesn't name another sibling tool to use for different scenarios, only states that this is the only restart available.

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