List all albums

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. The description only adds the authenticated-user scoping note; it says nothing about result size, pagination, or ordering, which is a meaningful gap for a listing endpoint.

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?

Very short and front-loaded, with the operation/tag metadata trailing. It repeats the title verbatim in the first line, a small redundancy, but nothing is bloated.

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 5-optional-parameter listing tool with no output schema, the description is adequate but leaves the filter capability completely unmentioned, so an agent reading only the prose would not know it can narrow by name, ownership, or sharing. Nothing about return shape is required, which keeps this from being worse.

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 every parameter is documented in the schema (including the notable 'assetId ignores other parameters' caveat), so the baseline of 3 applies. The description contributes no additional parameter meaning at all.

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 ('List all albums') and adds scope ('available to the authenticated user'), which distinguishes it from immich_get_album_info (single album) and immich_create_album/immich_delete_album. However, it never mentions that the endpoint is filterable, so 'all' slightly oversells the scope.

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 prerequisites, and no named alternative (e.g., use immich_get_album_info when you already have an album ID). The agent must infer routing purely from the name.

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