restart_ha

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively warns about the disruptive nature ('Temporarily disrupts all Home Assistant operations') and mentions the return value ('Result of restart operation'), which are crucial for understanding this tool's impact. It does not detail aspects like authentication needs or rate limits, but covers the core behavioral trait well.

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 highly concise and well-structured: it starts with the core action, includes a critical warning upfront, and ends with return information. Every sentence earns its place by adding essential value without any waste or 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's complexity (a disruptive restart operation), no annotations, no output schema, and 0 parameters, the description is mostly complete. It covers the purpose, warning, and return value, but lacks details on what the 'Result' entails (e.g., success/failure indicators) or any prerequisites, leaving minor gaps.

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 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and effects. A baseline of 4 is applied as it compensates adequately for the lack of parameters by providing other relevant context.

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 specific action ('Restart Home Assistant') with the resource explicitly named. It distinguishes itself from siblings like 'get_version' or 'system_overview' by being the only tool that performs a restart operation, not just querying or listing information.

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?

The description provides clear context for when to use this tool via the warning about disrupting operations, implying it should be used cautiously. However, it does not explicitly state when NOT to use it or name alternatives (e.g., 'call_service_tool' might offer similar functionality), which prevents a perfect score.

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