Retrieve notifications

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only the raw endpoint mapping (GET /notifications, tag: Notifications), which is provenance rather than behavioral context — nothing about default filtering, ordering, or pagination.

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 title is restated twice ('Retrieve notifications' followed immediately by 'Retrieve a list of notifications'), so one of the three lines is pure redundancy. The endpoint/tag line is metadata rather than guidance.

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?

A simple read-only list tool with complete schema coverage and full annotations is adequately served, but with no output schema the description could have said what a notification record contains or how the list is returned. Nothing critical is missing for correct invocation.

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% with four optional, fully documented parameters (id, type, level, unread), so the baseline is 3. The description adds no additional meaning about how those filters combine or behave.

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 ('Retrieve a list of notifications'), which is clearer than the bare title 'Retrieve notifications'. It does not explicitly differentiate itself from the sibling immich_get_notification (singular) or immich_get_notification_template_admin, though 'list' implies a collection.

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 guidance on when to use this tool versus immich_get_notification (single fetch) or immich_update_notifications. No preconditions, no mention of the optional filters that would select this tool in practice.

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