Create a notification

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description's only added behavioral context is the admin-tagged endpoint, which implies elevated authorization needs; it says nothing about what side effects a notification has or whether recipients can see it immediately.

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-loads the operation and scope. There is minor redundancy between the title line and the first description sentence, plus a metadata line, but nothing wasteful.

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 7-parameter tool with a nested free-form "data" object, two enums, and no output schema, the description is minimal. It never explains the notification types/levels or what the data payload should carry, leaving the agent to guess at the substantive part of the call.

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 the baseline is 3, and the schema entries are largely placeholders ("title (request body)") so there is little to build on. The description only hints at the userId requirement via "for a specific user" and never explains the meaning of the data object, type, or level enums.

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 ("Create a new notification") and adds scope ("for a specific user"), plus the underlying endpoint POST /admin/notifications. It does not differentiate from adjacent siblings like immich_update_notification or immich_delete_notification, but the core purpose is unambiguous.

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 statement of when to use this tool versus alternatives such as immich_update_notification, immich_delete_notification, or immich_get_notifications, and no prerequisites. Usage is only implied by the name and admin tag.

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