reboot

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

While the annotation already marks this as destructive, the description adds the critical behavioral detail that the reboot only occurs when confirm=True. This informs the agent of a safety mechanism and enables appropriate action. It does not contradict the annotation.

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 short sentences, each with essential information. The first states the action, the second states the prerequisite. No wasted words.

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 tool with no output schema, this description provides sufficient context: what it does and what condition triggers the action. It does not describe return values or post-reboot effects, but those are largely implicit for a reboot operation.

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 only lists 'confirm' with a default of false and no description, but the description clarifies that confirm must be true for the reboot to happen, giving semantic meaning beyond the schema. This compensates for the 0% schema coverage.

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 verb ('Reboot') and resource ('the NAS'), making it immediately obvious what action it performs. It distinguishes itself from sibling tools like 'shutdown' and 'restart_stack' by naming the specific target (NAS).

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 instructions imply this tool is for rebooting the NAS and note that confirmation is required, but they do not explicitly address when to use it versus alternatives like 'shutdown' or 'restart_stack'. No exclusions or broader usage context are provided, so it's clear but lacks alternative comparison.

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