Reload core configuration

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

Annotations cover safety profile (non-destructive, idempotent, not read-only), and the description adds meaningful behavioral context beyond them: it calls homeassistant.reload_all, fans out to all reloadable components, re-reads YAML from disk, and crucially does not wait for or report per-component results.

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-loads the core purpose, then uses clearly labeled sections (Use when / Not for / Returns). Every sentence earns its place, including the return note that warns the call is fire-and-forget.

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 system-level reload with zero parameters and an existing output schema, the description supplies everything needed: what it does, when to use it, when to avoid it, named alternatives, and the non-blocking behavior of the call.

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?

Tool takes zero parameters, so the baseline is 4 per the rubric. The description correctly avoids inventing parameter semantics; no additional meaning is needed or possible.

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 (reload core Home Assistant configuration) and scope (without restarting). Explicitly distinguishes itself from siblings system_restart_ha and system_reload_integration, so an agent can route correctly without opening schemas.

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?

Provides explicit 'Use when' (YAML for automations/scripts/scenes/groups changed, fast no-downtime reload) and 'Not for' (full restart cases, single integration) with named alternative tools. Nothing is left to inference.

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