Cleanup Deleted Blobs

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with 'destructive cleanup' and 'permanently release.' It adds a safety caution about confirming necessity, which goes beyond the annotation flag.

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 two sentences, front-loaded with the core action, and each sentence provides essential information: what it does and when to use it. There is no filler or repetition.

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 simple two-parameter tool with rich annotations and an output schema, the description covers the action, scope, and safety condition. It is complete enough for an agent to understand when and how to invoke it, though it relies on the schema for parameter details.

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 100%, with both workspaceId and confirmWorkspaceId fully described in the schema. The tool description adds no additional parameter-specific context, but the schema already provides sufficient meaning, so the baseline 3 applies.

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 uses a specific verb ('permanently release') and resource ('blobs that were already marked deleted'), clearly differentiating it from `delete_blob` and other workspace tools. It precisely states both the action and the precondition.

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 provides an explicit condition for use ('should be used only after confirming deleted blobs are no longer needed') and categorizes the tool as destructive cleanup. It does not explicitly name alternatives, but the phrasing implies a follow-up to deletion, which gives clear context.

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