Retrieve activity statistics

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 safety profile is covered. The description adds that the operation returns counts of likes and comments, which is useful context beyond the annotations, but it says nothing further about the response shape or scoping behavior.

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?

Three short lines, front-loaded with the purpose and immediately followed by the return semantics; the operation/tag line is metadata but compact. No filler or repetition of the title beyond the opening line.

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 simple read-only statistics endpoint with 100% schema coverage and annotations covering the safety profile, the description is sufficient: it conveys purpose and return content. No output schema exists, so no return-structure explanation is required.

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 both parameters (albumId, assetId) are already documented in the schema. The description's phrase 'for a given album or asset in an album' loosely mirrors those two parameters but adds no format or constraint detail, so the baseline 3 applies.

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 specific verb and resource (retrieve activity statistics) and clarifies the return value: counts of likes and comments for an album or an asset in an album. This distinguishes it from the listing sibling immich_get_activities, but it does not name that sibling 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?

Usage is implied by the description of what is returned (like/comment counts for an album or asset), but there is no explicit when-to-use guidance, no prerequisites, and no named alternative versus immich_get_activities or immich_get_album_statistics.

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