instance_reset_password

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is covered. The description adds useful effect context — the current password is replaced by the value supplied in the request body — but omits side effects, permission requirements, and the fact that the instance may need a restart; it also says "the password that you provided in the body" while the body actually takes a `secretId` reference, which is misleading.

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 opening line duplicates the title/endpoint, and the second sentence then restates the same purpose before adding the one new fact (the password is replaced). Front-loading is fine, but the redundancy costs a sentence that earns nothing.

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 non-idempotent mutation with a nested body and no output schema, the description covers the basic effect but omits what the caller should expect afterwards (restart requirement, timing), permission/authentication needs, and the surprising presence of SSH key and cloud-init fields in a "reset password" call.

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 all three parameters are documented in the schema and the baseline is 3. The description adds nothing about `instanceId` or the nested body fields, and notably does not explain that `sshKeys`/`userData` are also accepted alongside the password reset.

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?

States a specific verb and resource ("Reset password for a compute instance / resource referenced by an id") and includes the REST endpoint, so the agent knows exactly which operation this is. It does not, however, differentiate itself from the sibling tool `reset_password` (which appears to target user accounts), leaving a real name-collision ambiguity unresolved.

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 contains no when-to-use/when-not guidance, no prerequisites (e.g. required instance state, whether a reboot is needed), and no mention of the similarly named sibling `reset_password` that an agent could easily pick by mistake. Usage is only inferable from the verb itself.

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