shutdown_container

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

Annotations indicate non-readOnly and non-destructive, consistent with a shutdown operation. The description adds that the shutdown is graceful and includes a timeout parameter behavior, though it does not detail side effects or authorization beyond the risk level requirement.

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 a single sentence with an essential prerequisite, front-loading the key information. No unnecessary 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?

Given the output schema exists (though not shown), the description suffices for a simple shutdown operation. It covers the action, resource, and risk requirement, making it complete.

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?

Input schema has 100% coverage with clear descriptions for all three parameters (node, vmid, timeout). The description does not add meaningfully beyond the schema, so baseline score of 3 is appropriate.

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 'Gracefully shutdown an LXC container,' specifying the action (shutdown) and resource (LXC container). This distinguishes it from siblings like stop_container (likely force-stop) and shutdown_vm (for VMs).

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 notes 'Requires PROXMOX_RISK_LEVEL=lifecycle,' which informs the agent of a prerequisite. While it does not explicitly list alternatives or when-not to use, the sibling context implies it is for graceful shutdown of LXC containers, as opposed to stop_container.

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