Update notifications

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description usefully adds that this operates in bulk over a list, but does not explain what readAt=null does (mark unread?) or what happens to ids not found.

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?

Front-loaded and short, with the core action in the first real sentence. There is mild redundancy between the title echo 'Update notifications' and 'Update a list of notifications', and the trailing 'Immich operation' line is boilerplate, but overall it is efficient.

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 two-parameter update tool with annotations already carrying the safety and idempotency profile and no output schema, the description is sufficient to invoke correctly. The main residual gap is the precise semantics of a null readAt, which is minor.

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%, so the baseline is 3, though the schema's own descriptions are trivial ('ids (request body)', 'readAt (request body)'). The phrase 'bulk-set the read status' adds some meaning about readAt's role, but does not clarify that readAt null likely clears/unsets the read state.

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+resource ('Update a list of notifications') and adds the scope qualifier 'bulk-set the read status', which distinguishes it from the singular sibling immich_update_notification. It is clear what the tool does, though it never names the singular alternative explicitly.

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?

Usage is implied by 'bulk-set the read status of notifications', suggesting it is the multi-item path, but there is no explicit when-to-use vs when-not, no mention of immich_update_notification, and no prerequisites. The agent must infer the bulk-vs-single split.

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