create-vm-enhanced

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

With no annotations, the description carries full behavioral burden. It only mentions creating and updating context, but fails to disclose destructive nature, concurrency behavior, error handling, or side effects. The phrase 'automatically update infrastructure context' lacks specificity.

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 of 8 words is highly concise, front-loading the core purpose. However, it may be too terse given the complexity of the tool; it earns its place but could benefit from minor expansion on the automatic update aspect.

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?

Tool has 9 parameters, 4 required, no output schema, and no annotations. The description is too brief to fully inform an agent about the operation's scope, side effects, or return values. Missing guidance on what 'update infrastructure context' entails.

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%, so baseline is 3. The description provides no additional meaning beyond schema; it does not explain parameter formats, relationships, or selection criteria. No added 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 'Create VM in Proxmox' (specific verb+resource) and adds 'automatically update infrastructure context', distinguishing it from sibling tools like create-vm-template. The purpose is immediately clear.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for VM creation with automatic context update, but does not state exclusions, prerequisites, or compare to related tools like create-vm-template or update-context-after-operation.

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