reinstall_instance

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

The annotations declare destructiveHint=false, but the description describes reinstalling the instance with a new image, which strongly implies replacing or destroying existing instance state. The description does not disclose data loss, downtime, or other critical side effects, creating a safety contradiction.

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 short, front-loaded, and free of filler. It states the endpoint and the main capability in two compact sentences.

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?

For a reinstall operation, the description omits essential operational context such as whether existing data is destroyed, whether the instance must be stopped, and what happens to networking or attached resources. The schema is rich, but the description is not complete enough for safe invocation.

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%, so the schema already explains instanceId and the body fields. The description adds a high-level mention of new image, SSH keys, root password, and cloud-init, but does not add syntax or format details beyond the 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 gives a specific verb and resource: reinstall a specific compute instance. It also names the endpoint and the core action of using a new image, making it distinguishable from siblings such as create_instance or instance_restart.

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 explains what the tool can do but does not say when to use it versus alternatives such as create_instance, instance_restart, or instance_rescue. No prerequisites or when-not conditions are provided.

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