vm_reconfigure

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

Discloses write operation, undo capture mechanism, and dry_run preview. Without annotations, the description carries the burden and adequately covers key behaviors, though return values are omitted.

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?

Very concise: one-line action tag, a short paragraph, then bulleted args. Front-loaded with key info, no wasted words, easy to parse.

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?

Covers main usage and undo behavior, but lacks description of return values and error conditions. For a 6-parameter tool without output schema, more detail on expected output would improve completeness.

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?

Each parameter is explained: vmid as numeric ID, cores/memory as optional new values, dry_run as preview, target as Proxmox target, node as optional. Some parameters like 'target' could be more detailed, but overall adds value beyond 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 it changes a VM's cores and/or memory, with explicit verb and resource. It distinguishes from sibling tools like vm_resize_disk and vm_config by focusing on core/memory reconfiguration.

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?

Provides clear instructions: provide at least one of cores/memory, use dry_run to preview. Lacks explicit comparison to alternatives or when not to use, but gives sufficient context for typical usage.

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