reset_service_password

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

Annotations only set destructiveHint=true. The description adds critical behavioral details: live operation via qemu-guest-agent, no reboot/data loss, immediate credential invalidation, secret value handling, and the confirm safety check. No contradictions 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?

Description is front-loaded with key action and constraints. All sentences are informative, but slightly verbose. Could be trimmed without losing meaning, but still effective.

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 tool with 3 required params and no output schema, the description covers all contextual needs: when to use, scope requirements, parameter semantics, side effects, and safety confirmations. No gaps identified.

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 coverage is 100% with descriptions for all three parameters. The description adds value beyond schema: password is secret/never echoed, confirm requires explicit approval, and service_id source (list_services). Minor improvement would be noting the exact UUID format.

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 the action (reset root password), the target (running cloud VM via qemu-guest-agent), and distinguishes from sibling tool set_service_password for legacy VPS. It also clarifies it's not a reboot/rebuild, making the purpose unambiguous.

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?

Explicitly states when to use (cloud VM with Nova UUID) and when not to (legacy VPS, directing to set_service_password). Provides prerequisites like 'services:write' scope and warns about the confirm flag requirement for irreversible actions.

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