Reboot Homey

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

Annotations already indicate destructive and idempotent behavior. The description adds valuable context about the 2-3 minute downtime and typical problem scenarios. It does not contradict the annotations and improves transparency beyond the structured data.

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?

Three short sentences, each adding distinct value: what it does, how long it takes, and when to use it. No filler or redundancy. Perfectly front-loaded with the action.

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 simple no-parameter tool, the description is complete. It covers the operation, downtime, and use case. No output schema exists, so no return-value explanation is needed. The context is sufficient for an agent to select and invoke the tool correctly.

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 the baseline is 4. The description does not need to explain any input semantics. It correctly omits parameter information, and the empty schema is fully covered.

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?

Clearly states the action ('Reboot the Homey Pro') and the specific resource. Differentiates from sibling tools like restart_app (which restarts an app, not the whole device). The description adds 'Pro' and purpose context, going beyond a mere restatement of the title.

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?

Provides explicit use cases: 'resolve stale devices or Z-Wave/Zigbee mesh issues after firmware updates.' Also conveys the downtime expectation. No explicit exclusion or alternative is mentioned, but the context is clear enough for a tool with no close sibling (restart_app is distinct).

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