supervisor_restart_host

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

Since no annotations are provided, the description carries full weight. It discloses the destructive nature ('VERY DANGEROUS') and the confirmation requirement. However, it does not explain the full impact (e.g., service downtime, need for reconnection).

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 extremely concise (10 words) with no unnecessary verbiage. It front-loads the action and follows with a critical warning and condition.

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?

While the tool is simple (1 param, output schema exists), the description omits what happens after reboot (e.g., system restart, agent must wait). It is minimally adequate but could improve with post-action context.

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 schema has 0% description coverage, so the description must add meaning. It does: it tells that 'confirm' must be true for the tool to execute, which is critical and not obvious from the default false value.

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 action ('reboot') and the target ('host machine'), leaving no ambiguity. It explicitly differentiates from sibling restart tools (e.g., 'supervisor_restart_core') by specifying 'host'.

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 warns 'VERY DANGEROUS' and requires 'confirm=True', giving clear guidance on when to use (only with confirmation). It does not explicitly list alternatives or when not to use, but the danger implication is strong.

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