Restart App

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the symptom context for when a restart helps, but does not disclose side effects such as interrupted flows, brief device unavailability, or the response shape. Reasonable given annotation coverage, but not rich.

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, purpose front-loaded, followed by the motivating symptom and the dependency for obtaining the ID. No wasted text.

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 single-parameter action with annotations covering safety and a fully documented schema, the description supplies the missing decision context (symptom, ID source). Only minor gaps remain, such as side effects on running flows or app state after restart.

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?

Schema description coverage is 100% and already includes the pattern and example IDs, so the parameter is fully documented structurally. The description's example ('com.fibaro') and list_apps pointer duplicate or only lightly extend the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Restart a Homey app') and is clearly distinguishable from siblings such as enable_app, uninstall_app, and reboot_homey. An agent can select it without opening the schema.

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?

Gives a concrete trigger ('useful when devices from that app are unresponsive') and routes the agent to list_apps to obtain the ID. It stops short of explicit exclusions (e.g., when to prefer reboot_homey over an app restart), so it is clear but not fully comparative.

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