Change password

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a non-idempotent mutation. The description adds the current-user scope and the underlying endpoint mapping, but says nothing about side effects—notably what invalidateSessions does to active sessions. Adds modest context beyond structured data.

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 title and a single well-scoped sentence, plus an operation/tag line useful for routing. No wasted prose, though the endpoint metadata is somewhat redundant with the name.

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 security-sensitive mutation with no output schema, the description omits key operational context: that the current password is required, what invalidateSessions does to other sessions, and whether the change is reversible. Annotations cover the safety profile but not these behavior details.

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%, so baseline is 3, but the descriptions are tautological ("password (request body)", "invalidateSessions (request body)") and the prose adds no meaning—especially for invalidateSessions, whose behavior is left entirely unexplained by both schema and description.

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 and resource ("Change the password") and narrows scope to the "current user," which distinguishes it from admin tools like immich_update_user_admin that act on other users. It's clear without needing the schema, though it doesn't explicitly name a sibling it replaces.

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?

No guidance on when to use this versus immich_change_pin_code, immich_update_my_user, or the session-management tools. No prerequisites stated, such as needing the existing password or the consequences of the operation.

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