proxmox-execute-container-command

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

The description discloses the underlying SSH mechanism, the exact pct exec invocation, the prerequisite that the container must be running, and the required environment variables. This adds meaningful operational context beyond the minimal annotations (readOnlyHint false, openWorldHint false) without contradicting them.

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?

Three focused sentences with the main purpose front-loaded, followed by prerequisites and configuration. Minor redundancy exists between the first sentence (via SSH + pct exec) and the second sentence (Uses SSH key... and runs pct exec), but each sentence still contributes useful operational detail.

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?

For a 3-parameter command-execution tool with no output schema, the description adequately covers how to invoke it and what is required. It does not mention return values or error behavior, but the prerequisites, authentication, and execution method are sufficiently explained.

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 100% for all three parameters, so the schema already defines node, vmid, and command. The description adds no parameter-specific semantics beyond what the schema provides, so the baseline of 3 applies.

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 a specific verb ('execute'), resource ('shell command inside a running LXC container'), and mechanism ('SSH + pct exec'). It explicitly targets containers, which distinguishes it from the sibling proxmox-execute-vm-command without requiring schema inspection.

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?

It gives clear context: the container must be running, and SSH must be configured via environment variables. However, it does not explicitly call out the sibling proxmox-execute-vm-command for VM use cases, leaving the VM/container split implicit rather than stating when-not-to-use.

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