proxmox_node_disk_admin

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

Without annotations, the description carries the full burden for behavioral transparency. It labels operations as 'Destructive' but fails to elaborate on specific implications: data loss, irreversibility, permission requirements, or side effects. More detail is needed for such high-risk 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?

The description is extremely concise: a single sentence followed by a clear mapping of actions to meanings. Every phrase earns its place, 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 destructive tool with no output schema and no annotations, the description is lacking. It does not mention return values, error conditions, or side effects, leaving the agent without sufficient context for safe invocation.

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 75%, with the action parameter lacking description. The tool description compensates by listing and explaining the two enum values, adding crucial semantics beyond the schema. Node and disk are already described in the schema.

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 'Destructive disk operations' and enumerates the two actions (init_gpt, wipe) with brief explanations, directly indicating the tool's purpose. It distinguishes from sibling tools like proxmox_node_disk (likely read-only) and proxmox_vm_disk (VM-level).

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it mention prerequisites (e.g., disk unmounted) or post-conditions. Such guidance is especially important for destructive operations.

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