restart_virtual_machine

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

The description lacks behavioral details beyond the verb 'Restart'. It does not mention prerequisites (e.g., VM must be running), if it forces a reboot, or any side effects. With no annotations, the description carries the full burden, which it fails to meet.

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 a single sentence that states the core action, so it is concise and front-loaded. However, it is overly brief and omits important details, making it minimally acceptable.

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 complexity of virtual machine management, the description is severely incomplete. It does not explain the restart behavior, prerequisites, or output. With no annotations and zero parameter coverage, the agent cannot reliably use the tool.

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%, yet the description adds no information about the parameters (name, cluster, namespace). The agent must rely solely on parameter names and lack of descriptions, making it difficult to know what values to provide.

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 the verb 'Restart' and resource 'VirtualMachine', making the basic action clear. However, it does not explicitly distinguish from sibling tools like 'start' or 'stop', though the term 'restart' implies rebooting a running VM.

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 is provided on when to use this tool versus alternatives such as start_virtual_machine or stop_virtual_machine. The agent is left to infer usage from the name alone.

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