Unlink all OAuth accounts

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

Annotations already declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false). The description adds useful targeting detail ('associated with user accounts in the system'), clarifying what gets affected, but does not disclose reversibility, user impact, or confirmation requirements beyond what annotations provide.

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?

Short and front-loaded, with the operation line providing endpoint and tag context. There is minor redundancy between the title line and the sentence 'Unlinks all OAuth accounts associated with user accounts in the system', but overall it is efficient.

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 zero-parameter bulk admin mutation, the description covers the operation, scope, endpoint, and tag. It omits operational context such as reversibility, consequences for affected users, or whether any users are skipped, which would help an agent understand the impact.

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?

The tool takes zero parameters and schema description coverage is 100%, so the baseline of 4 applies. The description adds no parameter information, but none is needed.

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 ('Unlink'), resource ('OAuth accounts'), and scope ('all ... in the system'), which distinguishes it implicitly from the singular sibling immich_unlink_o_auth_account. However, it does not explicitly name the sibling or contrast the two operations, so it falls 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?

Provides no when-to-use guidance, no conditions for selecting this tool over alternatives like immich_unlink_o_auth_account, and no prerequisites beyond the 'admin' tag. The context is implied only by the operation endpoint.

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