Get time buckets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the word 'minimal' (hinting at a compact payload) and otherwise restates the operation; it says nothing about response shape, pagination, or what a bucket contains.

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?

It is short, but the first line merely repeats the title and the second line restates it again ('Get time buckets' / 'Retrieve a list of all minimal time buckets'), so the content is somewhat redundant rather than front-loaded with information.

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 read tool with 15 filtering parameters and no output schema, the description should explain what a 'time bucket' is and roughly what is returned. It leaves the core concept undefined and gives the agent nothing to reason about the response, so it is incomplete for the tool's complexity.

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 87%, so the 15 filter parameters (bbox, orderBy, visibility, isTrashed, etc.) are already well documented in the schema. The description adds no parameter meaning whatsoever, which is acceptable only because the schema does the heavy lifting — the baseline 3.

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 verb ('Retrieve') and resource ('time buckets'), but 'time buckets' is never explained, and it fails to distinguish itself from the closely named sibling immich_get_time_bucket (singular). An agent seeing both tools cannot tell which one it needs from this text 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 when-to-use guidance, no prerequisites, and no mention of the singular sibling immich_get_time_bucket as an alternative. The only routing hint is the raw REST path and tag, which is not usage guidance.

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