Shutdown Server

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

The description adds context that the shutdown is graceful and via ACPI, beyond the destructiveHint annotation. However, it does not mention potential outcomes (e.g., if server is already off, or OS ignores ACPI).

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?

One sentence, front-loaded with action and resource, no redundant 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?

With no output schema and no return value description, the description is adequate for a simple action but could mention the response (e.g., action object) for completeness.

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 single parameter 'id' is fully described in the schema as 'Server ID'. The description adds no extra meaning about how to obtain or format the ID, and schema coverage is 100%, so baseline 3.

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 a specific verb ('Send an ACPI shutdown signal') and resource ('graceful OS shutdown'), distinguishing it from sibling power tools like power_off (hard power off) and reboot.

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 implies use for a graceful shutdown via ACPI but does not explicitly compare to alternatives like power_off or reset, nor state when not to use it.

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