start_guest

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

Annotations already indicate this is a non-read-only operation (readOnlyHint: false), and the description adds no extra behavioral context such as side effects, permission requirements, or failure scenarios. With minimal annotation coverage, the description carries little additional transparency beyond the simple action.

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 concise sentence that is front-loaded with the action and target. No unnecessary words or repeated information.

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?

This is a simple one-parameter tool with an output schema present, and the description conveys the core purpose clearly. It does not specify prerequisites or edge cases, but for a straightforward start operation, the information is sufficient. Slightly lacking in usage guidance but overall complete for the tool's simplicity.

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 a single required parameter 'vmid' with no description, and the description does not explicitly explain it. However, the parameter name is self-explanatory as a VM ID, and the description 'Start a stopped VM or container' implies the vmid identifies which guest to start, adding some context beyond the raw schema.

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 'Start a stopped VM or container.' clearly states the action (start), the resource (VM/container), and the condition (stopped). It distinguishes from siblings like stop_guest, shutdown_guest, reboot_guest, and suspend_guest by focusing on the start operation.

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 when a VM or container is stopped, but provides no explicit guidance on when not to use it or how it differs from related operations like resume_guest. The phrase 'stopped VM or container' gives some context, but it's not clearly differentiated from alternatives.

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