Accept a cluster group request

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the mutation profile is largely covered. The description adds the real-world effect (the caller joins the group), but omits who is permitted to accept, whether the request record is consumed afterward, and what happens if it is expired or already accepted.

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?

Very short and front-loaded: the effect sentence comes before the REST/route metadata. The repeated title as the first line is mildly redundant with the tool name/title, but nothing is padded.

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 one-parameter mutation with annotations covering safety and no output schema, the essentials are present, but the description leaves out the accept-side prerequisites (caller must be the invited party), post-accept side effects, and failure modes, which an agent would need to call this correctly.

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 coverage is 100% for the single required id parameter (uuid format), so the schema carries full documentation. The description adds no semantics about the id beyond what the schema already states, making the baseline 3 appropriate.

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 (accept) and resource (cluster group request), and the second line clarifies the effect: joining the cluster group the request targeted. This distinguishes it from immich_delete_cluster_group_request and immich_create_cluster_group_request without needing the schema, 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 description implies the prerequisite that a request must already exist, but gives no explicit when-to-use guidance, no exclusions, and no pointer to the alternatives (delete the request instead, or list requests first with immich_get_cluster_group_requests).

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