Delete a user

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, fully covering the safety profile. The description adds nothing beyond them: it does not say what is destroyed (assets, albums, shared links), whether deletion cascades, whether it is reversible, or that admin privileges are required.

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?

It is short and the action is front-loaded, but the phrase 'Delete a user' is duplicated across title and body, and the raw endpoint line adds little. The size is fine; the redundancy is the flaw.

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 destructive admin mutation with no output schema, the definition should explain the blast radius and any auth requirement. Instead it only echoes the title, leaving an agent without the information needed to call it safely.

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%, so the schema already documents both parameters, giving a baseline of 3. The description adds no syntax or semantics for the ambiguous 'force' flag, so it neither helps nor compensates.

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 restates the title verbatim ('Delete a user') twice, which is a tautology rather than added meaning. The only new content is the raw endpoint 'DELETE /admin/users/{id}', which does not help an agent distinguish this from siblings like immich_delete_user_license, immich_delete_user_onboarding, or the undo counterpart immich_restore_user_admin.

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 when-to-use guidance, no mention of prerequisites (admin scope), and no reference to alternatives such as immich_restore_user_admin or soft-delete options. The agent is left to infer everything about when this tool applies.

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