attach_iso_to_vm

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

Discloses write operation, replacement behavior, works on/off state, audit log location, and error conditions beyond annotations, which only indicate not read-only and open world.

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 clear sections: operation, behavior details, prerequisite, audit info, parameter descriptions. Efficiently uses space 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 annotations and output schema exist, the description covers enough context: behavior, error cases, and parameter details. Complements structured fields well.

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?

Adds detailed meaning for each parameter: vm_name as exact vCenter name, iso_ds_path with bracket format example, target as optional from config. Schema had no descriptions, so this is highly valuable.

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 mounts a datastore ISO into a VM's virtual CD-ROM drive, and distinguishes from sibling tools like browse_datastore which is for finding ISOs.

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?

Provides guidance to find ISOs first with browse_datastore, explains behavior with existing CD-ROMs and IDE controller requirement, and notes target can be omitted. Does not explicitly list when not to use.

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