shutdown_nas

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

With no annotations, the description adds the requirement for an environment variable, indicating safety implications. However, it does not disclose behavior if the variable is unset or other side effects, leaving some gaps.

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?

Extremely concise: one sentence plus tags and requirement. Front-loaded with the action, 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 simple destructive tool with no parameters and an output schema (not shown but known), the description covers purpose and a key precondition. It could mention output handling, but the output schema exists to cover that.

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 input schema has zero parameters, so baseline is 4. The description adds no param info, which is acceptable as none exist.

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 action ('Shut down (power off)') and the resource ('the NAS'), distinguishing it from sibling tools like reboot_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?

It explicitly mentions a prerequisite (SYNOLOGY_ENABLE_POWER_CONTROL=true) which guides when to use, though it doesn't explicitly state when not to use (e.g., for restarting) but the sibling context implies differentiation.

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