reboot_nas

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

With no annotations, the burden is on the description. It discloses a prerequisite (SYNOLOGY_ENABLE_POWER_CONTROL) and tags [control][power] hint at the action type, but lacks detail on potential side effects like service disruption or reboot duration.

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 extremely concise with one sentence plus a tag. The core action is front-loaded, and every part contributes information without waste.

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?

Given the low complexity (no parameters, output schema exists), the description adequately covers the action and a key prerequisite. It could mention immediate effects like system restart or downtime, but is generally complete for the tool's simplicity.

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 and schema coverage is 100%, so no additional parameter information is needed. The description correctly does not add redundant detail; baseline for zero params is 4.

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 explicitly states 'Reboot the NAS', clearly indicating the action (reboot) and resource (NAS). It distinguishes from sibling tools like 'shutdown_nas' which performs a different action.

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 mentions a required configuration (SYNOLOGY_ENABLE_POWER_CONTROL=true) but does not provide guidance on when to reboot vs shutdown or other alternatives. The usage context is implied rather than explicit.

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