esxi_configure_vm

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds genuinely useful behavioral context beyond that — '未传字段不变' clarifies partial-update semantics — but omits the critical dry_run-defaults-to-true preview behavior and any permission requirements.

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?

Two tight sentences, front-loaded with the action and scope, ending with the partial-update rule. Every clause earns its place with no filler.

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 9-parameter destructive mutation tool with 0% schema coverage, the description is too thin: it never addresses dry_run (which silently defaults to a preview), expected_name concurrency semantics, or permission requirements. The existing output schema spares it from explaining return values, but the input-side gaps remain significant.

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 parameter meaning. It maps to roughly 6 of 9 fields (cpu, cpu_mhz_limit/reservation, memory_mb, memory_mb_limit/reservation) but never explains the critical dry_run flag (default true) or the required vm_id / expected_name parameters.

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 (修改/modify) and resource (VM CPU/内存) and enumerates the affected fields (核数、MHz limit/reservation、MB limit/reservation). It is distinguishable from siblings like esxi_rename_vm and esxi_power_vm, though it does not explicitly differentiate itself from esxi_vm_hardware.

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 on when to use this versus alternatives, no prerequisites, and no mention that dry_run defaults to true (so the default call is a no-op preview). The only usage-relevant statement is the partial-update rule '未传字段不变'.

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