Delete Blob

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavioral detail: deletion is recoverable by default and only permanent when bypassing recovery. It stops short of mentioning the confirmKey safeguard, which would make it a 5.

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, the core action front-loaded and the conditional flag guidance second. No filler, though the second sentence could be slightly tighter.

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?

Output schema exists and all four params are documented, so the description needn't explain return values. The recoverable-vs-permanent semantics are covered; the only gap is the absence of the confirmKey requirement and sibling differentiation.

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 already explains permanently ('permanently delete instead of marking it deleted') and confirmKey. The description's 'bypass recoverable deletion' phrasing reinforces the default-versus-permanent distinction but adds little beyond the schema, so 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?

Specific verb+resource ('Delete a blob') scoped to AFFiNE workspace storage, so it is clearly distinguishable from cleanup_blobs by intent. It does not explicitly name the sibling, keeping it below a 5.

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 second sentence hints at when to use permanently=true ('only when the blob should bypass recoverable deletion'), which is useful guidance for the flag. However, it never says when to call delete_blob vs cleanup_blobs, nor notes the confirmKey prerequisite, so usage context is only implied.

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