proxmox_backup

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

No annotations provided. Description only notes permission requirement and lists actions but does not disclose whether operations are synchronous, side effects (e.g., destructive delete), or state changes. Insufficient behavioral context for a tool with multiple actions.

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?

Single sentence with front-loaded purpose. No redundant information. Efficiently communicates core function and requirement.

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 9 parameters and no output schema, description is too brief. Does not clarify which parameters are required for specific actions (e.g., archive for restore/delete), nor explain parameter dependencies. Incomplete for the tool's complexity.

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 89% (high). Description adds overarching context that parameters pertain to guest backups but does not explain parameter relationships or requirements beyond schema. Baseline of 3 is appropriate as description adds minimal semantic 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?

Description clearly states verb 'manage', resource 'guest backups', and enumerates actions (create, list, restore, delete) and guest types (VMs, LXC containers). It effectively distinguishes from sibling tools like proxmox_guest_snapshot by focusing on backup operations.

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 'requires elevated permissions' as a prerequisite but does not specify when to use this tool versus alternatives (e.g., proxmox_guest_snapshot for snapshots, proxmox_storage_content for storage listing). No explicit exclusions or comparisons to sibling tools.

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