proxmox_management

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

With no annotations, the description should disclose behavioral traits. It lists operations like stop_vm (hard-stop) and delete_snapshot, which are destructive, but does not flag them as such or mention authorization needs, side effects, or idempotency. The return format is given, but behavioral warnings are missing.

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 structured with sections for operations, return format, and examples, which aids readability. However, it includes a redundant 'RATIONALE' label and is longer than necessary, containing some redundant phrasing.

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 the complexity (9 parameters, multiple operations) and no schema descriptions, the description is incomplete. It adequately covers operations and return format but fails to explain non-trivial parameters like iso, cores, memory, and disk_size, leaving significant gaps for the agent.

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?

The input schema has 9 parameters with 0% schema description coverage, so the description must explain all parameters. The description only covers 'operation' and 'vmid' via examples, leaving iso, name, cores, memory, disk_size, description, and snapshot_name unexplained. This severely limits parameter understanding.

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 explicitly states it is a consolidated tool for all remote Proxmox operations and lists 10 specific operations, making the purpose clear. However, it does not directly differentiate from sibling tools like vm_management or snapshot_management, which may overlap.

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 only mentions the prerequisite of PROXMOX_HOST being configured but provides no guidance on when to use this consolidated tool versus the more specific sibling tools, nor any scenarios where the tool should not be used.

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