force_shutdown_vm

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

With no annotations, the description carries the full burden and delivers: it warns 'DESTRUCTIVE', equates it to pulling the power cord, and discloses risks of data loss and filesystem corruption. It also explains the confirm safety mechanism, going beyond basic expectations.

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 compact, front-loaded with a warning, and uses a clear structure with an Args section. Every sentence provides necessary information without redundancy or fluff.

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?

Despite having an output schema (not shown), the description covers purpose, safety, usage alternative, and parameter details sufficiently for a destructive tool. It anticipates key questions and provides adequate context for safe invocation.

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 0%, so the description must compensate. It explains confirm's required behavior and default false, but vm_id is only described as 'The VM identifier', adding minimal value over the parameter name. Still, the confirm explanation is crucial and meaningful.

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 states 'Immediately force-stop a virtual machine' with a clear verb and resource. It explicitly distinguishes from sibling shutdown_vm by advising graceful shutdown first, making the tool's distinct purpose unambiguous.

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?

It provides explicit guidance on when to use this tool ('Use shutdown_vm for graceful shutdown first') and clarifies that confirm must be true to execute, otherwise a preview is returned. This gives clear context and an alternative.

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