Delete assets

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it never says whether deleted assets go to trash or are permanently removed, whether the `force` flag changes that, or what authorization is required — meaningful context for a destructive bulk operation.

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?

Very short and front-loaded, but the first line merely repeats the title verbatim before the sentence that adds information, which is mild redundancy rather than a functional flaw.

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 destructive, multi-asset delete with no output schema, the description should at minimum clarify trash-vs-permanent semantics and the effect of `force`. Given the complexity of the operation and its irreversibility, the current text leaves the agent under-informed.

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 both `ids` and `force` are documented in the schema, establishing the baseline of 3. The description contributes no additional meaning, notably nothing about what `force` actually does.

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 states a specific verb and resource ('Delete assets', 'Deletes multiple assets at the same time') and the underlying operation (DELETE /assets), so the agent knows exactly what it does. It does not, however, distinguish itself from the many other delete_* siblings in the namespace.

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?

No guidance on when to use this versus alternatives such as immich_delete_asset_file, immich_delete_duplicate(s), or immich_restore_assets. There is no mention of prerequisites, permissions, or the recovery path after deletion.

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