Delete Blob

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

Annotations already mark destructiveHint=true, so the description adds value by disclosing that normal deletion is recoverable and permanent deletion bypasses that. This is useful behavioral context beyond the annotations. No contradiction with annotations.

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 purpose. It is concise with no filler, and every sentence earns its place.

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 tool's complexity (4 params, output schema, annotations), the description is complete enough. It covers the primary action and the permanent-deletion nuance. The output schema and annotations cover return values and safety profile, so no additional explanation is needed.

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%, so the schema documents all parameters. The description adds a note about when to use permanent deletion, which relates to the permanently and confirmKey parameters, but does not explain them further. Baseline 3 is appropriate.

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 a blob from AFFiNE workspace storage' with a specific verb and resource. It distinguishes from sibling tools like upload_blob and cleanup_blobs by targeting a single blob deletion. The permanent flag nuance adds clarity.

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 gives clear context for deleting a blob and conditional guidance for the permanent flag ('Set permanently only when the blob should bypass recoverable deletion'), but does not explicitly mention alternatives or when not to use this tool. It provides some usage direction, though no exclusion criteria.

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