Retrieve workflow templates

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that results depend on installed plugins (consistent with openWorldHint), but says nothing about return format or whether an empty result means no plugins are installed.

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?

The description is short and front-loaded, with the scoping detail ('provided by installed plugins') up front. The first line merely restates the title and the trailing 'Immich operation: GET /plugins/templates' is API metadata, so there is minor redundancy.

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 zero-parameter read-only tool the definition is largely adequate, and annotations cover the safety profile. With no output schema, however, the description never indicates what a template contains or what the response shape looks like, leaving that to inference.

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?

The tool takes zero parameters, so there is no parameter semantics burden; the baseline of 4 applies. The description correctly implies the call is unconditional with no filters.

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 names a specific verb and resource — 'Retrieve workflow templates provided by installed plugins' — which is clearer than the bare title. It does not, however, differentiate itself from nearby siblings like immich_search_plugins or immich_search_plugin_methods, so an agent must infer the boundary.

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 sibling tools that retrieve plugin data. The 'installed plugins' qualifier hints at scope but never tells the agent when this is the right call versus immich_search_plugins.

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