reinstall_service

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

The description fully discloses behavioral traits beyond the destructiveHint annotation: it is irreversible, wipes disk and reinstalls OS, retains IP, may return a one-time consolePassword (must be treated as secret). It also notes sshPublicKey only applies to cloud VM and password is never echoed/logged. No contradiction with annotations.

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 thorough but somewhat lengthy, though well-structured with front-loaded action, then requirements, then security notes. Every sentence adds value, but could be slightly tighter. Score 4 for being informative without excessive verbosity.

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 absence of an output schema, the description adequately explains the one-time consolePassword response behavior and all parameter details. It covers required and optional parameters, confirm flag, and security considerations, making it complete for a destructive reinstall 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 100%, and the description adds significant value: explains imageId as a curated OS template slug, confirms password/sshPublicKey optional, specifies confirm must be explicitly approved by user, and adds security caveats (password not echoed, one-time consolePassword).

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 what the tool does: 'Reinstall (rebuild from scratch) a service'. It specifies the resource (service) and action (reinstall/rebuild), and distinguishes from sibling tools like stop, reboot, deploy, and destroy by emphasizing full OS reinstall with data loss.

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 provides clear usage context: requires scope services:write, instructs to get service_id from list_services and imageId from list_os_templates/list_images, and mandates confirm:true only after user approval. It warns about irreversibility but does not explicitly state when not to use or list alternative tools.

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