Restart Domoticz

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the description needs only add context. It adds the invocation guardrail 'Requires confirm=True', but does not explain the impact on running processes or expected side effects beyond what the annotation indicates.

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?

Two sentences with zero verbiage. The action is front-loaded, and the only extra detail is the essential confirmation constraint. Every word contributes.

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 one-parameter, destructive tool with a full input-schema description, annotations, and an output schema, the description provides the one thing an agent cannot infer elsewhere: that confirm must be true. No additional rules or hidden context are needed for a correct call.

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 schema covers 100% of the single parameter with its own description/default, but the description's 'Requires confirm=True' is a meaningful addition: it tells the agent the default false is not enough and the value must be true for the operation to proceed.

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 states 'Reboot server', a specific verb and resource, and the title clarifies it restarts Domoticz. None of the sibling tools perform a system reboot, so an agent can distinguish this tool without opening its 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?

The description gives no guidance on when this tool should be used versus alternatives, nor does it mention any preconditions beyond confirm=True. 'Requires confirm=True' controls invocation, but not when to call the tool or when not to choose it.

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