attach_drive

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

No annotations provided. Description mentions only the action and preconditions, but does not disclose side effects, success/failure indicators, or behavior on existing attachments. Minimal beyond the obvious.

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?

Extremely concise: two sentences plus structured parameter list. No redundant or extraneous information.

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 preconditions and parameter origins, but lacks description of return value, postconditions, or confirmation of successful attachment. Adequate given no output schema.

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 has 0% description coverage, so description fully compensates by explaining each parameter's purpose and constraints (name: must be stopped, drive_id: from list_vm_drives, source_path: path).

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 action (attach), the resource (ISO/disk image to removable drive), and distinguishes from siblings as no other tool performs this operation.

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 explicit precondition (VM must be stopped) and indicates source for drive_id (list_vm_drives). Lacks explicit alternatives or when-not-to-use, but context is clear.

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