vm_create

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

Annotations are absent, so the description must disclose behavioral traits. It includes '[WRITE][risk=medium]' indicating mutation and risk level, but does not explain what 'minimal' entails, whether changes are reversible, or error handling behavior. More detail on permissions or side effects would improve transparency.

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 concise with a clear purpose sentence, an argument list, and a tag for write/risk. Every sentence contributes information without redundancy, making it easy to scan.

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?

Given 5 parameters, no output schema, and no annotations, the description covers parameter semantics partially but lacks return value information, error conditions, or notes on asynchronous behavior. It is adequate for basic use but not fully comprehensive.

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 0%, so the description adds value by explaining parameters: cluster_ext_id from cluster_list, target as Prism Central target, default values for num_sockets (1) and memory_bytes (4 GiB). However, it omits details like name uniqueness constraints or accepted formats for memory_bytes.

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 'Create a minimal VM on a cluster' which specifies the verb and resource. It distinguishes from sibling tools like vm_list, vm_get, vm_update, vm_clone, and vm_delete, which serve different 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?

The description provides basic parameter explanations but does not explicitly state when to use this tool vs alternatives like vm_clone. It lacks guidance on prerequisites or scenarios where this tool is not appropriate, such as when a pre-existing VM configuration is needed.

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