Restart device

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

The description explicitly calls the operation 'Destructive', while the annotations declare `destructiveHint: false`. This is a direct contradiction about the tool's behavioral profile, which is serious for a reboot operation.

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 short and front-loads the endpoint and action. It contains no filler, though the vague warning fragment could be more precise without adding length.

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 reboot tool, the description identifies the action and endpoint but fails to mention service interruption, authentication requirements, or scope of impact. Worse, its 'Destructive' claim conflicts with the annotations, leaving the agent with an inaccurate behavioral picture.

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 are no parameter semantics for the description to document. The schema is empty and the description appropriately does not invent parameter details.

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 gives a specific verb (reboot) and resource (HDHomeRun), plus the exact endpoint `/sys/restart self`. It is immediately clear what the tool does and no sibling tool performs a restart.

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 only guidance is the vague phrase 'use with care'; there is no explanation of when to use this tool versus alternatives, no prerequisites, and no exclusions. The warning does not tell an agent how to decide whether restarting is appropriate.

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