pve_vm_resize_disk

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

No annotations provided, so description carries full burden. It discloses side effects (disk enlargement, filesystem separate growth), waiting behavior, and return format. No contradictions.

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?

Well-structured with a one-line summary followed by details. All sentences add value, though slightly lengthy. Could be slightly more concise.

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?

Given presence of output schema and four parameters, description is complete: covers side effects, usage constraints, return fields, and source endpoint. No gaps.

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 0%, but description compensates fully: explains vmid, disk (with examples), size (relative/absolute, units, grow-only constraint), and node (optional, auto-resolved). Adds significant meaning 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 grows a disk of a VM or container, specifies applicable types (QEMU VMs and LXC containers), and explains the key parameters. It distinguishes itself from sibling tools by focusing specifically on disk resizing.

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 usage context (grow only, with relative or absolute size) and mentions that filesystem must be grown separately. Could be more explicit about when to use this vs. other configuration tools, but still good.

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