hostodo_reinstall_vm

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

With no annotations provided, the description fully carries the burden. It discloses the destructive nature ('deletes and rebuilds the guest disk'), the fact that it starts the VM, and that it returns a one-time root password. The behavioral information is clear and non-misleading, though it could mention prerequisites like VM state.

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 two sentences: first sentence states purpose and prerequisite, second covers scope and side effects. It is front-loaded with the key verb 'destructively' and contains no redundant information. Every sentence earns its place.

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 4 parameters, no output schema, and no annotations, the description covers purpose, prerequisites, side effects, and return value. It lacks details about error handling or exact return format, but overall it is complete enough for an agent to use the tool 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 schema covers 100% of parameters with descriptions. The tool description does not add new meaning beyond the schema, simply restating the confirmation phrase and ssh_key_id optionality. Per guidelines, baseline 3 is appropriate when schema coverage is high and description adds minimal extra value.

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 explicitly states 'Destructively reinstall one owned Hostodo VPS to an enabled OS template', using a specific verb and resource. It clearly distinguishes from sibling tools like hostodo_restore_snapshot or hostodo_power_vm by emphasizing the destructive reinstall action.

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 directs the agent to call hostodo_list_templates first to discover valid template IDs, and specifies the required scope and confirmation phrase. However, it does not explicitly mention when not to use this tool or exclude alternative approaches.

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