Shutdown guest (graceful)

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

Describes 'gracefully' and 'via ACPI/guest OS', indicating soft shutdown. No annotations provided, so description carries full burden; but it doesn't detail behavior on success/failure, timeout handling, or required permissions.

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 sentences, no redundant words. Front-loaded with action and key differentiator. Highly concise.

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 no annotations or output schema, description should offer more context. It covers core function and sibling preference but omits error scenarios, result format, and prerequisites.

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 coverage is 100% with both parameters described in schema. The description adds no additional meaning beyond what the schema already provides for 'guest' and 'timeout'.

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 uses specific verb 'shut down' and identifies resource 'VM or container'. It explicitly differentiates from the sibling `stop_guest` by calling this the 'safe way', making the purpose clear.

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?

States 'prefer it over stop_guest', giving clear usage preference. However, lacks explicit when-not conditions or failure scenarios (e.g., when to fall back to stop_guest).

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