remove_disk_from_vps

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

Annotations already indicate destructiveHint=true, so the destructiveness is known. The description adds the specific requirement of confirm=true and the permanence of the action, which are not captured by the annotations. This provides actionable behavioral context that an agent needs to safely invoke the tool.

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, tightly packed sentence that leads with the core action and immediately conveys the critical constraint (irreversibility and confirmation). There is no filler or redundancy; every word contributes meaning.

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?

For a destructive operation with no output schema, the description lacks essential context such as prerequisites (e.g., whether the VPS must be stopped or the disk must be detached), error conditions, and what happens to data on the disk. It also fails to explain any of the parameters, making it insufficient for an agent to safely and correctly invoke the tool without additional information.

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%, so the description must compensate by explaining parameters, but it does not mention vps_id, disk_uuid, or confirm roles. The phrase 'requires confirm=true' implies one parameter's purpose but offers no detail on the others, leaving the agent to guess from names alone.

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 states a specific action ('Permanently remove') and a clear resource ('a disk from this VPS'), distinguishing it from siblings like add_disk_to_vps and list_vps_disks. The emphasis on irreversibility further delineates its destructive nature from read-only operations.

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 is provided on when to use this tool versus other disk-related tools, nor any prerequisites or contraindications. The only hint is the requirement for confirm=true, but the description does not explain the context or alternatives, leaving usage nearly entirely to inference.

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