system_stop_ha

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

The description warns about the need for manual restart and explains the safety prompt behavior. With no annotations provided, the description adequately discloses the destructive nature and safety mechanism.

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 extremely concise with exactly two sentences, no wasted words. It front-loads the purpose and includes the warning and parameter guidance efficiently.

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 tool with one parameter and an output schema, the description covers purpose, warning, and parameter behavior completely. No missing information is apparent.

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 parameter 'confirm' has no schema description, but the tool description fully explains its effect: setting confirm=True proceeds with the stop, otherwise a safety prompt is returned. This compensates for the 0% schema coverage.

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 'Stop Home Assistant', which is a specific verb and resource. It distinguishes from sibling tools like system_restart_ha by focusing on stopping, not restarting.

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 explicitly mentions the need for a manual restart and the confirm parameter behavior. It provides clear context for when to use, but does not explicitly mention alternatives like system_restart_ha.

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