Delete stacks

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description confirms the batch/list nature but says nothing about what actually gets destroyed (e.g., whether member assets are deleted or merely unstaked), which would be valuable extra context for a destructive op.

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?

Front-loaded and short; the batch semantics appear immediately. The title is restated in the first line and the 'Immich operation' trailer is boilerplate, but the whole thing is small and wastes little space.

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 one-parameter batch delete with destructive/idempotent annotations already present and no output schema, the definition is largely sufficient. The one meaningful gap is whether deleting a stack affects its contained assets, which an agent might reasonably need.

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 there is only one parameter, but the schema's own text is thin ('ids (request body)'). The description adds real meaning by clarifying these ids are stack IDs and that the operation accepts a list, exceeding the baseline for a fully-covered 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?

States a specific verb (delete) and resource (stacks) and adds the batch scope ('multiple stacks by providing a list of stack IDs'), which distinguishes it from the singular immich_delete_stack sibling even though that sibling isn't named. Clear and specific, but no explicit sibling differentiation.

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?

The description implies batch deletion via 'list of stack IDs,' but gives no explicit when-to-use guidance, no prerequisites, and no routing to immich_delete_stack for single-stack deletion or immich_search_stacks for finding IDs.

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