Guest Agent Filesystem Freeze

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

Annotations mark destructiveHint=true, but the description goes no further. It does not explain the consequences of freezing (e.g., guest may become unresponsive until thaw), the need to thaw after a freeze, or the side effects of fstrim. The phrase 'requires elevated permissions' hints at sensitive operations but does not disclose behavioral traits beyond the annotation.

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 a single, compact sentence that leads with the purpose and immediately lists the valid operations. It is efficient and easy to parse, though it could benefit from a brief explanation of each operation or a note on when to use it. No unnecessary words.

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?

With no output schema and four distinct operations each having significant side effects, the description is incomplete. It does not explain what the tool returns (e.g., status results), nor does it warn about the need to thaw a frozen filesystem to avoid data corruption. The 'requires elevated permissions' is the only operational caution. For a tool that can disrupt a guest, this lack of context is inadequate.

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 descriptions cover node and vmid, giving the operation parameter only an enum without explanation. The description repeats the enum values and adds the generic 'requires elevated permissions' note, which applies to the operation. It does not clarify what each operation does (e.g., what 'fstrim' achieves), but the listing does help map the enum. Given 67% schema coverage, the description adds marginal value.

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 the tool manages filesystem freeze via the QEMU agent and enumerates the four operations (status, freeze, thaw, fstrim). It distinguishes itself from sibling agent tools like exec, power, and info by focusing on freeze operations. However, the verb 'Manage' is somewhat generic, and a more precise phrasing would list the actions directly.

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 provides no guidance on when to use this tool versus alternatives, such as when freezing before a snapshot or when trimming after deletion. It only notes 'requires elevated permissions,' which is a prerequisite, not a usage context. Sibling tools like proxmox_agent_exec handle other guest operations, but no comparison or selection criteria are mentioned.

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