vm_apply_plan

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

Discloses sequential execution, failure behavior (stops immediately, keeps plan file, returns rollback_available flag), and success behavior (deletes plan file). No contradiction with annotations.

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 well-structured with a clear title line and bulleted Args section. However, it is slightly verbose; minor trimming could improve conciseness.

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?

Lacks explicit output schema, but describes return of rollback_available flag. Could mention more about return value structure or open world behavior, but adequate for a plan execution tool.

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?

With 0% schema description coverage, the description fully explains both parameters: plan_id is the ID from vm_create_plan, and target is an optional vCenter/ESXi target. This adds critical context beyond the schema.

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 'Execute a previously created plan step by step.' The verb 'execute' and resource 'plan' are specific, and it distinguishes itself from sibling tools like vm_create_plan and vm_rollback_plan by describing the execution step and post-failure behavior.

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?

Explicitly states when to use (after vm_create_plan), what happens on failure (stops, returns rollback_available flag), and directs to ask user and call vm_rollback_plan if needed. Provides clear context and alternatives.

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