vm_create_plan

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

Description discloses write nature ([WRITE]), validation/checks, generation of rollback info, and non-destructive behavior (returns plan). Adds value beyond annotations which only give basic hints. No contradiction.

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?

Well-structured with front-loaded purpose, then triggers, behavior, allowed actions, example, return format, usage guidance. Efficient use of sentences without redundancy.

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 no output schema, description details return format (plan dict with keys). Explains validation and existence checks. Agent has all needed context to correctly invoke 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, description fully explains operations parameter: dict structure with 'action' key, allowed actions, example. Target parameter described as optional vCenter/ESXi target. Meaningfully supplements 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 creates an execution plan for multi-step VM operations. It specifies the resource (plan) and action (create), and distinguishes from siblings like vm_apply_plan which applies the plan.

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 mentions auto-triggering for 2+ steps or VMs, advises showing plan to user before calling vm_apply_plan, and lists allowed actions with example. Provides clear when-to-use and alternative guidance.

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