pdm_pve_lxc_power

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

Without annotations, the description discloses mutation, dry-run (PLAN) default, confirm flag for execution, and task-backed submission. Could mention idempotency or failure modes, but the provided information is sufficient for safe use.

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 with three sentences, each carrying essential information. Front-loaded with 'MUTATION' and key verb and resource. 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?

For a power control tool, the description covers mutation nature, dry-run behavior, confirm flag, and task-backed returns. With an output schema present, no need to detail return values. Sufficient for agent to select and invoke correctly.

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 100%, so baseline is 3. The description adds context about the dry-run default behavior via confirm parameter, which is not obvious from schema alone. It also implies the action parameter accepts 'start', 'stop', 'shutdown', matching schema enums.

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 is a mutation for starting/stopping/shutting down a container on a PDM-registered remote. It distinguishes from siblings like pdm_pve_qemu_power (for VMs) and pve_guest_power (for direct cluster management) explicitly.

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?

Provides explicit guidance on when to use this tool versus alternatives (pdm_pve_qemu_power for VMs, pve_guest_power for direct cluster). Also explains the dry-run default behavior with confirm=True for execution, and task-backed nature.

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