Retrieve an album

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the underlying REST mapping (GET /albums/{id}) and tag, with no extra behavioral context like permission requirements or error behavior.

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 body is short and front-loaded, but the opening line "Retrieve an album" merely duplicates the title before the substantive sentence restates the same idea again, so a portion 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 simple read tool whose annotations cover safety and which has no output schema, the description is adequate to identify and call it. However, the unexplained key/slug parameters leave a real gap for a three-parameter tool with low schema coverage.

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 only 33%, so the schema does not carry the load. The description mentions only the ID ("by its ID") and says nothing about the key or slug parameters, leaving two of three parameters unexplained in both places.

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 ("Retrieve information about a specific album by its ID"), which distinguishes it from the bulk sibling immich_get_all_albums. It does not explicitly name any sibling as an alternative, so it stops short of the top band.

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 only implied: an agent infers it should call this when it already has an album ID and needs that album's details. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as immich_get_all_albums or immich_get_album_statistics.

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