Delete people

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. The description adds the bulk-multiplicity context but says nothing about consequences (e.g., what happens to associated faces/assets) or auth needs, so the added behavioral value is modest.

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 'Delete people' duplicates the tool title verbatim and the closing 'Immich operation/tag' line is template boilerplate. Small redundancy keeps it from being tight.

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 destructive tool the essentials exist, and annotations carry the safety profile. However, the description omits what deleting a person actually removes or affects, leaving room for an agent to underestimate impact; it is adequate but not complete.

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% for the single 'ids' parameter, so the schema already documents the UUID-array body. The description's 'list of people' loosely reinforces that ids is plural but adds no format or constraint detail; baseline 3 is appropriate.

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+resource ('Delete people') and clarifies the bulk scope ('Bulk delete a list of people at once'), which distinguishes it from the single-target sibling immich_delete_person. It falls short of naming that sibling explicitly, so an agent must infer the distinction from 'bulk' and 'list'.

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 phrase 'Bulk delete a list of people at once' implies usage (multiple people to remove in one call), but there is no explicit when-to-use guidance, no named alternative, and no preconditions such as required permissions or confirmation. Usage is only implied.

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