Shutdown container (graceful)

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

Annotations indicate a non-destructive mutation. The description adds 'graceful' and 'ACPI' context but does not disclose behavior regarding timeout, forceStop, or process handling. With annotations present, the description adds moderate value.

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 concise sentences that efficiently convey the core purpose and technical equivalence. 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?

While the purpose is clear, the description lacks parameter context and usage scenarios. Given 4 parameters and 0% schema description, the agent is left uninformed about key options like timeout and forceStop.

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 description provides no information about any of the 4 parameters (node, vmid, timeout, forceStop). With 0% schema coverage, this is a critical gap; the agent must rely solely on parameter names and types.

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 it performs a graceful shutdown via pct shutdown, equivalent to ACPI shutdown. This specifies the verb (shutdown), resource (container), and distinguishes from forceful stop (stop_container) and VM shutdown (shutdown_vm).

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 usage for graceful container shutdown but lacks explicit guidance on when to use vs alternatives like stop_container or shutdown_vm. No prerequisites or exclusion criteria are mentioned.

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