Delete a notification

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is fully covered by structured data. The description adds only the REST mapping (DELETE /notifications/{id}) and repeats the title, contributing no behavioral context such as whether deletion is permanent or what permissions are required.

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 content is padded: the title 'Delete a notification' is repeated verbatim as the first line, followed by a near-identical second sentence, plus a metadata line. Only the REST endpoint reference is non-redundant, so most of the text does not earn 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?

For a one-parameter delete with full annotation coverage and no output schema, the definition is minimally sufficient. However, it omits the irreversibility/alternative-tool context that would make an agent confident it is choosing the right delete variant.

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%, and the single id parameter is documented (format: uuid), so the schema carries the weight. The description adds nothing beyond the endpoint template echoing {id}, which fits the baseline 3 for high schema coverage.

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 (Delete) and resource (a notification), and 'a specific notification' implies single-item scope versus the bulk sibling. It does not explicitly name immich_delete_notifications, so the agent must infer single-vs-bulk from the wording alone.

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?

There is no when-to-use guidance, no exclusion, and no mention of the obvious alternative immich_delete_notifications for bulk deletion. The agent gets a purpose statement but nothing that routes it between the singular and plural tools.

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