supervisor_restart_core

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

With no annotations, the description carries full burden. It warns 'DANGEROUS' and specifies the need for confirm=True, which is good, but lacks details on side effects, downtime, or what exactly gets destroyed. It is adequate but not comprehensive.

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 with two sentences that convey essential information without any fluff. Every word serves a purpose.

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 simplicity of the tool (one parameter) and presence of an output schema, the description covers the basics. However, it does not explain what happens during the restart or provide any post-conditions, which could be useful for a dangerous 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 has one boolean parameter 'confirm' with default false, and the description adds critical context that it 'requires confirm=True', which is not evident from the schema alone. Schema coverage is 0%, so the description compensates well.

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 ('Restart') and the resource ('Home Assistant Core'), and it is distinguishable from sibling restart tools like 'supervisor_restart_addon' and 'supervisor_restart_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 mentions it is dangerous and requires confirmation, but does not provide any guidance on when to use this tool versus alternatives, such as 'system_restart_ha' or 'supervisor_restart_host'.

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