proxmox_agent_freeze

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

No annotations are provided, so the description carries the full burden. It mentions 'requires elevated permissions' and enumerates operations, but does not disclose side effects (e.g., freeze suspends I/O, thaw resumes, fstrim trims). This is adequate but not thorough.

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 of 15 words, front-loaded with purpose, no wasted words. Very concise and effective.

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 three required parameters and no output schema, the description provides the operation options and permission requirement. It lacks explanation of each operation's effect or return values, but it is adequate for a standard QEMU guest agent tool.

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 coverage is 67% (node and vmid have descriptions, operation only has enum). The description adds meaning by listing the operation values and stating the permission requirement, compensating for the missing schema description for operation.

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 manages filesystem freeze via QEMU agent and lists four operations (status, freeze, thaw, fstrim). It distinguishes itself from sibling tools that cover other QEMU agent functions (exec, file, hw, info, power, user).

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 implies when to use it (for freeze-related actions) and lists the operations, but does not explicitly state when not to use it or provide alternatives. However, the sibling tool names make the context clear enough.

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