n8n_list_workflow_templates

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

readOnlyHint=true already signals a safe read operation, and the description is consistent by saying 'List'. It adds that results include metadata and concern pre-built workflows, but it does not disclose pagination, ordering, or the scope of 'available'. For a read-only list tool, this is adequate but not rich.

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?

Two short sentences with the main action front-loaded and the second sentence adding a usage purpose. There is slight redundancy between 'available workflow templates' and 'what pre-built workflows are available', but no significant waste.

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 list operation with well-documented optional parameters, the description is mostly sufficient. The main gaps are the lack of distinction from n8n_search_public_templates and the vague return description, especially since there is no output schema.

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%, and both parameters (search and category) already have descriptive definitions in the schema. The description adds no parameter-level meaning, so the baseline of 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?

Clearly states the action ('List') and resource ('available workflow templates') and mentions that metadata is returned. However, it does not differentiate this from sibling tools like n8n_search_public_templates or n8n_get_workflow_template, and 'available' is ambiguous about whether these are built-in or public templates.

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 phrase 'Use this to discover what pre-built workflows are available' gives an explicit discovery use case. It does not mention alternatives or exclusions, so an agent receives no guidance on choosing between this and n8n_search_public_templates.

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