Delete Virtual_disk

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

The description goes beyond the destructive annotation by detailing exactly what cascading deletes entail (e.g., deleting a device removes interfaces, IPs, etc.). It emphasizes irreversibility and the need for confirmation, providing rich behavioral context.

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 concise and well-structured: it starts with the purpose, then provides warnings and return information. Every sentence adds value 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 the simple single parameter and the presence of annotations, the description is fully complete. It covers purpose, destructive behavior, cascade effects, user confirmation, and return value. No gaps remain.

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 coverage is 100%, and the description does not add additional meaning beyond the schema's description of the 'id' parameter. The baseline score of 3 is appropriate.

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 ('Delete'), the resource ('virtual_disk'), and the method ('by numeric id'). It effectively distinguishes this tool from the many sibling tools, including other delete tools for different objects.

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 explicitly warns about the destructive and irreversible nature, explains cascading deletes with examples, and advises confirming with the user. While it doesn't list alternative tools, it provides clear context for when to use this tool cautiously.

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