Decline a cluster group request

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only the 'pending' state qualifier and the underlying endpoint, with no detail on permissions, effects on the requester, or reversibility – modest added value against a lower bar.

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, but the title sentence is repeated verbatim in the description body and the following line restates the same action, so a third of the text is redundant. The API-operation trailer is useful metadata but not front-loaded content.

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 single-parameter delete whose annotations already disclose the destructive/idempotent profile and whose schema is fully documented, the description says enough to invoke correctly. Minor gaps remain (no mention of required permissions or the resulting state of the declined request).

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?

There is a single 'id' parameter at 100% schema coverage (documented as uuid format), so the schema carries all meaning. The description adds nothing about which id is expected beyond what the schema already provides, 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 (Decline/Delete) and resource (a pending request to join a cluster group), which an agent can distinguish from the many unrelated delete_* siblings. It does not explicitly name its opposite sibling immich_accept_cluster_group_request, so it stops short of full sibling differentiation.

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 gives no when-to-use or when-not-to-use guidance and never mentions the obvious alternative, immich_accept_cluster_group_request. The only usage signal is the word 'pending', which implies the request must still be pending but is not stated as a condition.

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