esxi_create_vm

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

Annotations already declare destructiveHint=true / readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: the VM is created empty with no OS installed, and clone/migrate are out of scope. It omits the notable dry_run=true default, which matters for a destructive tool.

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?

Three short sentences, front-loaded with the action and its required inputs, then constraints and exclusions. No filler, though the parenthetical parameter list is dense rather than elegant.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers scope, exclusions, and parameter sourcing, leaving only the dry_run default unaddressed.

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 must carry semantics, and it names 7 of the 8 parameters plus the datastore/network sourcing constraint. However it omits units (memory_mb, disk_gb), the guest_id default, and the dry_run flag, so it only partially compensates for the coverage gap.

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?

States a specific verb+resource (创建 VM / create VM) and enumerates the required inputs, then explicitly scopes out clone/migrate. An agent can distinguish this from siblings like esxi_rename_vm, esxi_configure_vm, or esxi_ovf_import without opening the schema.

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?

Gives clear preconditions: datastore and network must be explicitly supplied from query results (implying the list_datastores/list_networks siblings), and notes the name is the target itself so no expected_name is needed. It does not explicitly name which sibling to call for the lookup, so it falls just short of the top band.

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