system_reload_all

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

With no annotations provided, the description must inform the agent about side effects or safety. It only states 'Reload', which implies re-reading config files, but does not disclose whether this is a hot reload or requires a restart, or any potential impact on running automations. This is insufficient for a mutation tool.

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 a single concise sentence that effectively communicates the tool's purpose, listing examples of the configuration types involved. No wasted words.

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?

The tool is simple with no parameters, and an output schema is present, so the description's list of reloaded components is mostly sufficient. However, missing details about whether the reload is immediate or requires a restart slightly reduce completeness.

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 has zero parameters, and the input schema is fully documented (100% coverage). The description does not add parameter info because none exist, so a baseline score of 4 is appropriate.

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 tool reloads core configuration and lists specific components (automations, scripts, scenes, groups). This distinguishes it from sibling tools that reload individual components, such as automations_reload_automations or zones_reload_zones.

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?

No guidance on when to use this tool versus its more specific siblings. It does not mention that this is a bulk reload alternative to individual reload functions, nor does it indicate any prerequisites or post-reload actions.

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