proxmox_guest_resize

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

With no annotations, description must provide behavioral details. It only mentions 'requires elevated permissions', but lacks info on idempotency, destructiveness, reboot requirements, or hotplug capability.

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?

Single sentence, front-loaded with verb and resource, no unnecessary words. Every part is essential.

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 mutation tool without output schema or annotations, description is minimal. It does not explain return values, synchronization, or side effects like reboot, making it under-specified for complex VM operations.

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%, so baseline is 3. The description adds no additional parameter meaning 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?

Description clearly states verb 'Resize', resource 'VM/LXC CPU or memory', and includes the type parameter. This effectively distinguishes from disk resize tool (proxmox_guest_disk_resize) and 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?

Description implies usage for CPU or memory resizing, and mentions elevated permissions as a prerequisite. However, it does not explicitly state when to use this tool versus alternatives like disk resize or config update.

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