restart_home_assistant

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

With no annotations, the description carries the full behavioral burden. 'Fire-and-forget' usefully discloses that the call is asynchronous and does not confirm completion, but it omits material behavior: restart timing/delay, whether Home Assistant goes offline, and the blast radius of restarting the whole instance. That is important context for a tool that disrupts the entire system.

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?

Two short sentences, front-loading the action and its nature, followed by the condition that selects it. Every clause earns its place with no repetition of the schema.

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 zero-parameter, no-output tool, the definition covers what it does and when to invoke it, which is sufficient for correct selection. The remaining gap is behavioral detail about restart side effects, which a careful agent would want given there are no annotations to fall back on.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter semantics gaps exist.

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?

States a specific verb and resource ('Schedule a Home Assistant restart') and clarifies the operation's character as fire-and-forget. It implicitly distinguishes itself from the reload_config sibling by noting the affected entities 'have no reload service', so an agent can pick it apart from the reloader without opening a schema.

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?

Gives a concrete when-to-use trigger: after creating/updating/deleting notify groups or history_stats sensors. The clause 'which have no reload service' signals why this is needed instead of a reload, but the alternative tool (reload_config) is not named explicitly, so routing is slightly less crisp than it could be.

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