Restart Home Assistant

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

Annotations declare destructiveHint=true, but the description adds substantial context beyond them: 1-5 minute downtime, all automations unavailable, automatic config validation before proceeding, and the embedded-mode reply-before-restart behavior. It even documents the Claude Desktop timeout/approval workaround, which is operationally critical and unavailable elsewhere.

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?

Front-loaded with the WARNING and restart consequences, then alternatives, then the example — good ordering. The Claude Desktop workaround paragraph is lengthy and narrow, adding some bulk, though it is genuinely actionable for the agent.

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?

A mutation tool that could leave the server unreachable is fully covered: cost, duration, validation, embedded behavior, and the alternative path. An output schema exists, so return values need no elaboration.

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 100%, and the schema already documents that confirm must be True, so the baseline is 3. The description adds a concrete invocation example (ha_restart(confirm=True)) that reinforces correct usage, giving a small lift above baseline.

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+resource ("Execute a Home Assistant restart") and immediately distinguishes itself from siblings by naming ha_reload_core and ha_get_system_health. An agent knows exactly what this does versus the reload alternative.

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?

Explicit when-to-use (full restart) and when-not (config changes → ha_reload_core; pre-check → ha_get_system_health(include="config_check")). Alternatives and their selecting conditions are spelled out, not implied.

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