Resize Guest CPU/Memory

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

Annotations already mark the tool as non-read-only, destructive, and idempotent. The description adds a meaningful auth requirement ('requires elevated permissions') that is not present in the annotations or schema. It does not contradict the annotations, though it could disclose more about effects on running guests.

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?

A single sentence with no filler. It packs in the operation, resource types, type discriminator, and permission requirement in a compact, front-loaded way.

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 5-parameter mutation with no output schema, the description plus annotations cover the core invocation facts: what is resized, the required type discriminator, and elevated permissions. It does not explicitly state that at least one of cores/memory should be supplied, but the phrase 'CPU or memory' implies it, making this a minor gap.

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 80%, with node, vmid, cores, and memory already documented. The only uncovered parameter is 'type', and the description's 'type=vm|lxc' only restates the schema enum. The description adds no meaningful semantic detail beyond what the schema already provides.

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 specific verb ('Resize') and resource ('VM/LXC CPU or memory'), which cleanly distinguishes it from the sibling proxmox_guest_disk_resize. The 'type=vm|lxc' qualifier further scopes the target. This is more than a restatement of the title because it names the exact resource types involved.

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?

No explicit when-to-use guidance is given and no alternative tools are named. The description never mentions conditions for choosing this tool over related siblings like proxmox_guest_config_update or proxmox_guest_disk_resize. 'Requires elevated permissions' is an authorization note, not usage guidance.

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