machine_reset

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

The description exceeds the annotations by detailing concrete consequences ('user loses unsaved state'), the preview behavior of confirm=False, and the audit trail. This adds valuable context beyond the destructiveHint and readOnlyHint flags.

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 well-structured with a clear summary, followed by imperative safety/alternative notes, and a concise Args breakdown. Every sentence adds value 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 the destructive nature, 3 parameters, and no output schema, the description fully covers purpose, usage, parameters, and side effects. The preview mode is explained, and the alternative for graceful reboot is provided, making it complete for an agent to invoke correctly.

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?

With 0% schema description coverage, the description compensates fully by explaining each parameter: machine_ids references machine_list, confirm explains the boolean's preview/reset behavior, and target specifies its source from config.yaml. This is complete and actionable.

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 performs a 'Hard-reset' on 'desktop machine(s)', indicating a specific verb and resource. It immediately distinguishes itself from a graceful reboot by directing users to an alternative tool, making its 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 the tool: for hard resets, and explicitly states to use vmware-aiops for graceful in-guest reboots. It also explains the confirm flag's role in previewing versus acting, giving clear usage context.

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