Get the default configuration with user visibility

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read profile is covered. The description adds only the audience scoping ('visible to logged in users'); it says nothing about auth requirements or that a live server call is made.

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 operative sentence appearing immediately. The title line and the 'Immich operation'/'tag' trailer are mildly redundant metadata but do not bloat the description.

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?

A zero-parameter, read-only endpoint with annotations covering safety and no output schema to explain; the description conveys what is returned (default config values visible to logged-in users) well enough to call it. Naming the admin/public counterparts would make routing unambiguous.

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, so the baseline of 4 applies. There is no parameter syntax the description could usefully add.

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: retrieving default configuration values, scoped to properties visible to logged-in users. This differentiates it from the admin/public config-defaults variants by audience, though it never names those siblings explicitly.

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 'visible to logged in users' implies when this variant applies, but there is no explicit guidance distinguishing it from immich_get_config_defaults, immich_get_admin_config_defaults, or immich_get_public_config_defaults. Usage is left to inference.

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