Remove an asset from a stack

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the REST endpoint mapping, but crucially omits whether the asset itself is deleted or merely unlinked from the stack group, which is the key behavioral ambiguity for this operation.

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 title is restated as the first line and then paraphrased again in the second sentence ('Remove a specific asset from a stack'), which is redundant. It is short and front-loaded, but the duplication means not every sentence earns 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?

With only 2 fully-documented parameters and no output schema, little else is required. However, for a destructive stack operation the description should clarify the effect on the asset itself (unlink vs delete) and any auth/permission needs, which it does not.

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 coverage is 100% and both params are documented as uuid format. The description adds only a light mapping ('stack ID' and 'asset ID') that clarifies which parameter is which, which is marginal over the schema's format hints.

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+resource (remove an asset from a stack) and even maps it to the underlying REST operation DELETE /stacks/{id}/assets/{assetId}. This distinguishes it from siblings like immich_remove_asset_from_album and immich_delete_stack, though it never explicitly names those alternatives.

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?

It says how to call it (provide stack ID and asset ID) but gives no guidance on when to use this versus immich_delete_stack, immich_update_stack, or immich_remove_asset_from_album. No prerequisites or exclusions are stated.

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