Delete notifications

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, covering the safety profile. The description adds only the raw endpoint and tag metadata, saying nothing about permanence, whether IDs that don't exist cause errors, or any auth requirements — no value beyond the structured fields.

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?

It is short and front-loaded, but the first line simply repeats the tool title verbatim, and the 'Immich operation: DELETE /notifications · tag: Notifications' line is generator metadata that carries little decision value. Roughly half the text is redundant.

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 one-parameter bulk delete with full schema coverage and annotations that declare the destructive/idempotent profile, the description is adequate — an agent can call it correctly. Only minor gaps remain, such as behavior on non-existent IDs.

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% (a single required 'ids' array with uuid items), so the schema fully documents the parameter. The description adds no format, limit, or batch-size guidance beyond what the schema provides, which is the baseline 3 case.

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 and resource ('Delete notifications') and clarifies the bulk scope with 'Delete a list of notifications at once,' which implicitly separates it from the singular sibling immich_delete_notification. It stops short of explicitly naming that sibling, so differentiation requires a small inference.

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 phrase 'at once' hints at the bulk use case, but there is no explicit when-to-use guidance, no mention of the single-notification alternative, and no prerequisites or permission notes. An agent must infer the routing decision entirely.

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