add_vm_disk

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('attach') without revealing important behavioral traits such as whether the VM must be stopped, whether the operation is reversible, or what side effects occur. It lacks context that would help an agent anticipate risks.

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 a single, clear, and front-loaded sentence with no wasted words. It efficiently communicates the core purpose, though it could be slightly more informative without becoming verbose.

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 tool has 10 parameters and is a mutating operation on a VM, but the description offers no context about return values, prerequisites (e.g., VM must exist), or the impact of the operation. The lack of an output schema and the purely terse description leave the agent underinformed about how to use the tool effectively.

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 0%, and the description provides no information about parameters like 'storage', 'size', 'disk_type', or how they affect the operation. The description adds zero value beyond the raw schema, which fails to compensate for the lack of parameter documentation.

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 'Attach a new virtual disk volume to a VM' uses a specific verb ('attach') and resource ('virtual disk volume' to a 'VM'), clearly distinguishing it from sibling tools like resize_vm_disk and move_vm_disk. It fully captures the tool's function.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or comparisons with sibling tools like resize_vm_disk or move_vm_disk. The usage is only implied by the tool's purpose.

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