Get storage template options

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the underlying REST operation (GET /system-config/storage-template-options) and its 'System config' tag, which is useful provenance but no extra behavioral detail such as auth requirements or response characteristics.

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?

The description is short and front-loaded, and the REST-operation line adds concrete provenance. It is slightly redundant, repeating 'Get storage template options' in the title and then rephrasing it as 'Retrieve exemplary storage template options', but the brevity keeps it 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 no-parameter read tool whose annotations already carry the safety profile, the description is minimally adequate. With no output schema present, it could have explained what the returned template options look like or how they are used, but leaves that entirely to the caller's inference.

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 is 4. There is nothing for the description to disambiguate at the parameter level, and the empty schema is correct.

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 gives a verb ('Get'/'Retrieve') and resource ('storage template options'), so the basic operation is understandable. However, it is essentially a restatement of the tool name, and 'exemplary' is vague about what these options actually are. It does nothing to distinguish this from adjacent config-style siblings like immich_get_config or immich_get_admin_config.

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 prerequisites, and no mention of any alternative tool. An agent gets no signal about when this is the right call versus the many other get_* config tools in the sibling set.

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