Delete disk

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

Annotations already mark the tool as destructive and not read-only. The description adds crucial behavioral details: all data on the disk will be lost and the service immediately loses access. This goes beyond the annotations by specifying the exact consequences of the action.

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 three concise sentences, each delivering key information: purpose, critical warning, and API call. No unnecessary words. The structure is front-loaded with the primary action.

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 low complexity (1 parameter, no output schema), the description sufficiently covers the tool's behavior. It explains the effect on disk and service, and references the API endpoint. While it does not specify the return format, for a delete operation this is acceptable as typical REST responses are well-known.

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?

The schema has 100% coverage for the single parameter 'diskId', including an example and pattern. The description does not add additional meaning beyond referencing the disk ID. Baseline 3 is appropriate as the schema provides sufficient information.

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 'Delete disk' with a specific verb and resource. It expands on the purpose by clarifying it is a persistent disk attached to a service, distinguishing it from other delete tools for different resources. The mention of the REST API endpoint further solidifies the tool's action.

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 lacks explicit guidance on when to use this tool versus alternatives (e.g., other delete tools or update disk). It does imply usage context by noting that the disk is attached to a service and that data will be lost, but does not provide prerequisites or scenarios where deletion is appropriate.

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