create_lvm

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

The description does not disclose potential side effects such as data loss on the device or that node must be a Proxmox node. Annotations are absent, so the description carries full burden but provides minimal behavioral context.

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 short with a clear initial sentence and a bulleted list of arguments. It is efficient but could be better structured.

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 potentially destructive create operation, the description lacks important context about prerequisites, side effects, and when not to use it. The absence of annotations and low schema coverage make it 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?

Since schema description coverage is 0%, the description attempts to explain parameters (node, name, device, add_to_storage). However, the explanations are minimal and do not cover constraints like device format or naming uniqueness.

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 creates an LVM volume group on a device. However, it does not differentiate from sibling tools like create_lvmthin or create_zfs_pool, which have similar purposes.

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 guidance is provided on when to use this tool versus alternatives, nor are there prerequisites or conditions for safe usage.

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