proxmox_guest_disk_resize

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only notes elevated permissions, but fails to mention if resizing requires the guest to be stopped, whether it's destructive, or any side effects. This is insufficient for a mutation tool.

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 a single, efficient sentence with no superfluous words. It is appropriately concise, though it could benefit from slight elaboration without losing conciseness.

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?

The description lacks crucial context such as whether the operation requires the guest to be offline, what happens to existing data, or the return value format. Given zero annotations and no output schema, it is incomplete for a destructive resize action.

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 high (80%), so much parameter meaning is already captured. The description adds context for the 'type' parameter by clarifying VM vs LXC, but does not significantly enhance 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 clearly states the tool resizes guest storage for both VM and LXC container types, with a specific verb and resource. It distinguishes from sibling tools like proxmox_guest_resize by specifying 'disk' resize.

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 mentions 'requires elevated permissions', indicating a prerequisite, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. It implies usage context but does not list similar tools.

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