Reload the Hammerspoon configuration

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

The description fully discloses the reload scheduling mechanism, the reset of all in-memory state, and the specific interaction with hs_speak (stopping speech and the crash risk if a callback occurs post-reload). This is highly transparent.

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 concise (two sentences) and well-structured, covering purpose, usage, and important side effects without unnecessary verbosity.

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 lack of parameters and output schema, the description thoroughly covers the tool's behavior, scheduling, and edge case with hs_speak, making it complete for the user to understand the tool's implications.

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 no parameters, and the description appropriately omits any parameter-related details. There is nothing to explain, so the description fully addresses what the schema provides (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 clearly states the tool's function (reload ~/.hammerspoon/init.lua) and specifies when to use it ('after editing the user configuration'). It also explains the purpose of the scheduling and side effects, leaving no ambiguity.

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?

Explicitly instructs when to use the tool ('Use after editing the user configuration') and warns about the reset of in-memory state and the speech callback crash risk, providing clear guidance on appropriate usage.

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