proxmox_agent_file

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

Discloses the need for elevated permissions, a key behavioral trait. No annotations are present, so the description carries the burden; however, it does not describe side effects, concurrency, or error behavior.

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?

Extremely concise single sentence, front-loaded with the core action. No wasted 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?

No output schema exists, yet the description does not explain return values or behavior for read/write operations. Missing context for a tool with 6 parameters and potential side effects.

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?

Description adds little beyond the input schema—'operation=read|write' is already in the schema enum. Schema coverage is high (83%), so baseline of 3 is appropriate.

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 reads/writes files via QEMU agent and mentions the operation parameter, distinguishing it from sibling agent tools (exec, freeze, etc.).

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?

Mentions that elevated permissions are required, but does not provide explicit guidance on when to use this tool versus alternatives or when to use read vs write. Purpose is implicit.

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