vm_apply_plan

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

The description discloses important behaviors like deletion of the plan file on success, which contradicts the annotation destructiveHint=false. According to scoring rules, contradictions mandate a score of 1.

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 (5 sentences) and front-loaded with the action and key behavior, with no unnecessary words.

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?

The description covers execution behavior, failure handling, and rollback guidance. While it lacks explicit return format details, it sufficiently explains outcomes for a tool with no output schema.

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?

Despite 0% schema description coverage, the description explains both parameters (plan_id as the ID from vm_create_plan, target as optional vCenter/ESXi target), adding essential meaning 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?

The description clearly states the tool executes a previously created plan step by step, distinguishing it from sibling tools like vm_create_plan, vm_rollback_plan, and vm_list_plans.

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 explains the sequential execution and gives guidance on when to use vm_rollback_plan upon failure, providing clear context for alternatives, though it doesn't explicitly list when not to use this tool.

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