restart_remote

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

Since no annotations are provided, the description carries the burden of behavioral disclosure. It states that the tool sends no device commands and changes no configuration, mitigating safety concerns. However, it does not mention the dry_run default or potential service disruption during restart, leaving some behavioral context 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 three sentences, each serving a purpose: what the tool does, what it does not do, and when the two targets are needed. It is front-loaded and avoids redundancy.

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?

The tool is simple, with optional parameters and an output schema, so the description doesn't need to explain return values. However, it omits the crucial dry_run semantics, which could cause an agent to believe a restart occurred when the tool only echoed the action. This gap makes the description incomplete for safe autonomous invocation.

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 coverage is 0%, so the description must compensate. It defines the valid values for target and hints at their purposes, but it fails to explain the host and dry_run parameters, especially dry_run's default true, which is critical for the tool to actually perform a restart.

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 a specific verb (Restart), a resource (the remote), and the valid targets ('ui', 'core', 'system'). It differentiates itself from sibling tools like restart_integration by focusing on the remote-level restart and explicitly disclaiming device commands or configuration changes.

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 explains when to use each target: ui for repainting configuration changes and system after driver installation. It implicitly distinguishes this from send_command or configuration tools by stating it changes no configuration, but it does not explicitly name alternatives or conditions for choosing this tool over restart_integration.

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