List all plugins

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the auth-scoping note ('available to the authenticated user') and says nothing about pagination or result size, which is the kind of context that would add real value here.

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?

Short and front-loaded, with the purpose in the first line. There is mild redundancy between the title, the first line, and the second sentence, but no wasted filler.

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?

With no output schema and only 33% schema description coverage on 6 parameters, the description should clarify the role of those parameters and the shape of the returned list. Annotations cover the safety profile, so the gap is moderate rather than severe, but the definition is not fully self-sufficient.

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 only 33% across 6 parameters (id, name, title, enabled, version, description), and the description mentions none of them. It never explains whether these are filter criteria narrowing the plugin list or something else, so the description fails to compensate for the low schema coverage.

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 ('List all plugins' / 'Retrieve a list of plugins available to the authenticated user'), which is clear enough to distinguish it from the singular sibling immich_get_plugin. However, it does not explicitly differentiate itself from immich_search_plugin_methods or immich_search_plugin_templates, which an agent could plausibly confuse with a plugin listing.

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 explicit when-to-use guidance, no conditions, and no named alternatives. The phrase 'available to the authenticated user' hints at scope but the agent is left to infer that this is the list-all counterpart to immich_get_plugin.

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