proxmox_agent_exec

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

With no annotations, the description must disclose behavioral traits. It mentions elevated permissions for status but omits key details: how exec returns a PID, how status consumes it, error behavior, or that the command runs synchronously. Minimal transparency.

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?

Two short sentences, front-loaded with purpose, no extraneous words. Every sentence adds value. Highly concise.

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?

Despite high schema coverage, the description fails to explain parameter dependencies for each operation, return values, or how to sequence exec and status. Given 9 parameters and no output schema, the description is incomplete.

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 89%, so baseline is 3. The description adds no meaning beyond the schema; it only restates the operation enum values without explaining parameter relationships (e.g., exec requires command, status requires pid).

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 executes commands via QEMU agent and distinguishes two operations (exec, status). It uses a specific verb 'execute' and resource 'commands via QEMU agent', making it distinct from sibling proxmox_agent_* tools.

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 explains the two operations and notes elevated permissions for status, but lacks guidance on when to use this tool versus alternatives like proxmox_lxc_exec or proxmox_agent_file. It does not mention prerequisites or parameter dependencies for each operation.

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