pve_shutdown_container

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

No annotations are provided, so the description carries full burden. It mentions 'graceful' shutdown but doesn't disclose critical behavioral traits: whether this requires specific permissions, what happens to running processes, if data loss is possible, or how it interacts with timeouts and forceStop. The description is too minimal for a destructive operation.

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 with just three words, front-loaded with the core action. Every word earns its place: 'Shutdown' (action), 'container' (resource), 'graceful' (key behavioral trait). No wasted verbiage.

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 destructive operation with no annotations and no output schema, the description is inadequate. It doesn't cover prerequisites, side effects, error conditions, or what 'graceful' entails. Given the complexity of shutting down a container, more context is needed for safe use.

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?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying graceful behavior relates to timeout/forceStop, but doesn't explain their interaction. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb ('Shutdown') and resource ('a container'), specifying it's a graceful operation. It distinguishes from siblings like 'pve_stop_container' (which likely implies forceful stop) and 'pve_reboot_container', but doesn't explicitly differentiate them.

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?

No guidance on when to use this tool versus alternatives like 'pve_stop_container' or 'pve_reboot_container'. The description mentions 'graceful' but doesn't explain when graceful shutdown is preferred or what happens if it fails.

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