Update cloud-init drive

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

Annotations provide safety profile (readOnlyHint=false, destructiveHint=false) but description adds only that it regenerates the ISO. It does not clarify whether existing settings are overwritten or merged, whether the VM needs to be stopped, or when changes take effect. Additional context beyond annotations would improve transparency.

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?

Single sentence with clear verb and direct listing of parameters. Efficient and front-loaded, no filler. Slightly could structure information (e.g., separate required vs optional) but overall concise.

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 9 parameters and no output schema, the description provides a high-level summary but lacks completeness. It doesn't explain the effect on the VM (e.g., immediate reboot required), return value (success message?), or edge cases. Sibling tools exist but no positioning context.

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?

Schema description coverage is 78%, and the description simply lists parameter categories (user, password, etc.) without adding new semantics. For node and vmid, the description omits details that the schema lacks (no description for these required parameters). The description does not enhance understanding 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 it sets cloud-init parameters and regenerates the cloud-init ISO. The specific listing of parameters and the action 'regenerate the cloud-init ISO' distinguishes it from other VM tools, making its purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives like update_vm_config. Does not mention prerequisites (e.g., VM must have cloud-init enabled) or exclusions. The agent must infer usage from the name and description alone.

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