skypilot_storage_delete

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

The destructiveHint annotation already flags the write/destructive nature, so the bar is lower. The description usefully adds that it returns a request_id, implying an async operation the agent may need to poll via skypilot_get_request, but it says nothing about irreversibility, permissions, or what happens to bucket contents.

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?

Two short sentences, front-loaded with the action and resource, with no filler. It is efficient, though the trailing detail about request_id could be folded more usefully into behavioral context.

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?

An output schema exists, so return values need not be explained. However, for a destructive single-parameter tool, the description omits prerequisites, irreversibility, and how to use the returned request_id, leaving meaningful gaps.

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 0% and the single required parameter 'name' has no description in the schema or the tool description. The description implies 'name' identifies the storage object but does not say whether it is the storage name reported by skypilot_storage_ls, a bucket name, or an ID.

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?

States a specific verb ('Delete') and resource ('SkyPilot-managed storage object (cloud bucket)'), which is clearly distinguishable from siblings like skypilot_storage_ls and skypilot_volume_delete. It does not explicitly name a sibling, but the resource is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives (e.g., storage_ls to inspect first) and no prerequisites or warnings. The only implicit cue is the destructive nature, which is already carried by annotations.

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