start_virtual_machine

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

The description discloses the core behavior (setting spec.running=true) but does not elaborate beyond that. No annotations are provided, so the description carries the full burden. It lacks details about side effects, required permissions, or expected state of the VM before starting.

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, well-structured sentence with no unnecessary words. It front-loads the action and resource.

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 tool has an output schema (implied), the description still lacks contextual completeness. It does not explain the required state of the VM before starting, error conditions, or parameter usage. The 0% schema coverage and missing guidance on when to use the tool make it insufficient for an AI 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?

The input schema has three parameters (name, cluster, namespace) with 0% description coverage in the schema. The description does not mention any of these parameters, adding no meaning beyond the raw schema. This fails to compensate for the lack of schema descriptions.

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 action 'Start' on the resource 'VirtualMachine' and specifies the mechanism 'by setting spec.running=true'. This distinguishes it from sibling tools like stop_virtual_machine, restart_virtual_machine, and unpause_virtual_machine.

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 explicit guidance on when to use this tool versus alternatives (e.g., restart_virtual_machine). The usage is implied by the verb 'start', but there are no prerequisites, preconditions, or warnings about when not to use it.

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