Retrieve a stack

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

Annotations already declare readOnly=true, destructive=false, idempotent=true and openWorld=true, so the safety profile is fully covered by structured data. The description only adds the underlying HTTP mapping (GET /stacks/{id}) and the tag, which is operational metadata rather than behavioral context such as error behavior on a missing ID.

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 description is short and front-loaded, leading with the action. It is slightly redundant, though, repeating the title ('Retrieve a stack') before restating it as 'Retrieve a specific stack by its ID.'

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 single-parameter read tool whose annotations fully cover the safety profile and which has no output schema to explain, the description is largely complete. Its only real omission is any notion of failure behavior (e.g., an unknown stack ID).

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% (the single 'id' parameter is documented as a UUID), so the schema carries the parameter burden. The description merely restates that retrieval is keyed by ID, adding no new format or constraint detail beyond the schema.

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 specific stack by its ID') and pins the lookup key to the ID, which distinguishes it from list/search-style siblings like immich_search_stacks. However, it never explicitly contrasts itself with the other stack siblings (create/update/delete), so it stops short of a 5.

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 explicit when-to-use guidance or mention of alternatives. The phrase 'by its ID' weakly implies the caller must already hold a stack ID, but the description never says to use immich_search_stacks to obtain one, nor does it state any preconditions.

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