system_check_config

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

With no annotations, the description must fully communicate behavioral traits. 'Validate' suggests a read-only check, but it does not explicitly state that the tool is non-destructive, what happens on success/failure, or any side effects. The presence of an output schema partially mitigates this, but the description lacks sufficient behavioral detail.

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?

A single, front-loaded sentence that efficiently communicates the core action and context. Every word earns its place with no redundancy.

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 tool has no parameters and an output schema exists, the description is mostly complete. It clearly states the action and context ('before restart'), but could be enhanced by explicitly mentioning it is a pre-restart validation step.

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 zero parameters and 100% coverage. Per guidelines, baseline for 0 params is 4. The description adds no parameter details, but none are needed.

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 uses a specific verb 'Validate' and resource 'Home Assistant configuration', clearly distinguishing this tool from siblings like 'system_restart_ha' or 'services_reload_config'. It is not a tautology and immediately conveys the tool's purpose.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., configuration changes made) or that it should be run before restart. The context is only implied by the phrase 'before restart'.

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