Guest Agent User Management

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

The description adds the elevated-permissions requirementaint, which is useful beyond the annotations. However, it does not disclose that the existing password is overwritten, that the QEMU agent must be running, or any side effects beyond what destructiveHint and idempotentHint already imply. 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 short and mostly front-loaded, with no filler. The broad phrase 'Manage guest users' is less precise than the operation-specific detail, but the overall compactness helps an agent parse it quickly.

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 single-operation tool with no output schema, the description is minimally viable but leaves gaps: it does not state that the VM must be running, that the QEMU agent must be installed/active, or what result/confirmation the agent should expect. Annotations cover the destructive and idempotent nature, so the omission is not critical.

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 83%, so the schema already documents most parameters. The description adds little beyond restating 'operation=set_password,' which is already encoded as an enum. This meets the baseline but does not elevate meaning for parameters like crypted or username.

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 states a clear verb and resource: manage guest users via QEMU agent, and narrows the action to operation=set_password. It is clear enough to distinguish from agent info/exec/file siblings, though it does not explicitly name them or contrast with proxmox_guest_config_update.

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?

There is no explicit guidance about when to use this tool versus alternatives, and no exclusions are stated. The only contextual hint is 'requires elevated permissions,' which is a prerequisite rather than a use-case selector.

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