Reload the Hammerspoon configuration

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

With no annotations provided, the description carries the full burden of disclosure. It adds valuable behavioral details beyond a bare 'reload' statement: the reload is scheduled asynchronously so the call returns first, and it resets all in-memory state held by the configuration. This is substantive and useful for the agent to predict side effects.

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 two short sentences. The first sentence declares the purpose and resource; the second adds the crucial scheduling and state-reset behavior. Every word earns its place, and the key information is front-loaded.

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 zero-parameter, no-output-schema tool, the description fully covers purpose, usage timing, and side effects. It is self-contained and leaves no important gaps for an agent to guess about. Given the simplicity of the operation, it is complete.

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, so there is nothing to document. The baseline of 4 is appropriate since the description does not need to compensate for missing parameter information. It avoids over-explaining an empty schema.

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 explicitly states the action ('Reload') and the resource ('~/.hammerspoon/init.lua'), making it unmistakably distinct from sibling tools like hs_health or hs_list_windows. It clearly refers to the Hammerspoon configuration reload.

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?

It provides a clear use case: 'Use after editing the user configuration.' It does not explicitly mention when not to use or name alternatives, but for a configuration reload tool, the context is simple and well understood, and there are no obvious sibling tools that perform a similar function.

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