batch_deploy_from_spec

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

Annotations show readOnlyHint=false and destructiveHint=false. Description adds '[WRITE]' indicating mutation, sequential deployment, failure handling ('one VM's failure is recorded and the rest continue'), and auditing. Good additional context beyond 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?

Well-structured: summary line, usage guidance, behavioral details, then args and returns. No redundant sentences; every line adds value. Front-loaded with purpose.

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?

Covers all aspects: YAML spec structure, defaults and overrides, sequential behavior, error handling, auditing, parameter descriptions, and return format. Given complexity, description is complete.

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 compensates fully: explains spec_path as 'Local filesystem path to the deploy.yaml specification file' and target as 'vCenter/ESXi target name from config.yaml; omit to use the default target.' Clear and sufficient.

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 deploys multiple VMs from a YAML spec, using specific verb 'Deploy' and resource 'multiple VMs'. It distinguishes from sibling tools by listing alternatives for single VM deployments.

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 'Use for fleet provisioning' and lists when to prefer other tools like deploy_vm_from_template, vm_clone, etc. Provides clear context for when to use this tool versus alternatives.

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