Get the system configuration defaults

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context beyond that: it returns the default of EVERY system configuration property, which characterizes the breadth of the response — valuable since there is no output schema. It stops short of describing permissions/enumeration details.

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/route metadata last. The first line duplicates the title verbatim before the more informative second sentence, a minor redundancy, but nothing bloats the definition.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description supplies what remains needed: what is returned (defaults for every system config property) and the underlying endpoint. Only the distinction from sibling config-defaults endpoints is left unstated.

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 per the rubric the baseline is 4. There is nothing for the description to clarify, and it correctly avoids inventing parameter discussion.

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 states a clear verb+resource: retrieving default values for system configuration properties, and the second sentence scopes it to 'every system configuration property.' It is understandable without opening a schema, but it never distinguishes itself from close siblings like immich_get_admin_config, immich_get_config_defaults, or immich_get_public_config_defaults, which require inference from the name alone.

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 statement of when to call this versus the many neighboring config tools. The description names no alternatives and no conditions (e.g. 'use when you need factory values before applying a config change'), so an agent must infer usage from the tool name and the admin tag.

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