system_shutdown

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

Annotations already provide destructiveHint=true, but the description adds important behavioral context: the VM remains locked by this session and the guest cannot reconnect until external restart. It also mandates calling vm_unlock, which is beyond what annotations convey.

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 extremely concise, two sentences long, with the purpose front-loaded and the lock caveat following immediately. Every sentence provides critical information without redundancy.

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 that this is a simple tool with only two optional parameters and no output schema, the description covers the essential effect (shutdown), the critical lock state, and the required follow-up (vm_unlock). It omits parameter-specific behavior, but that is already penalized in parameter semantics. Overall, it is nearly complete for the tool's complexity.

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 schema has zero description coverage, and the description does not explain the meaning of 'force' or 'delay_seconds'. The agent receives no guidance on how these parameters affect the shutdown, leaving a significant gap in parameter understanding.

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 tool 'shuts down Windows 98', which is a specific verb+resource. It distinguishes itself from sibling tools like system_reboot by indicating a full shutdown with no automatic restart.

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 context (full shutdown, not reboot) by stating that the guest cannot reconnect until the VM is started externally. However, it does not explicitly name alternative tools or say when not to use it, so it lacks an explicit when-not condition.

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