n8n_get_workflow_template

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

The readOnlyHint annotation already covers the safety profile, and the description adds a meaningful behavioral detail: it can match templates intelligently rather than only retrieving by ID. It does not disclose specifics like matching criteria, behavior when both parameters are provided, or possible network/API dependencies, but the annotation lowers the burden.

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?

A single sentence covers both operation modes with no filler. The primary action is front-loaded, and the alternative path is clearly appended.

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?

Given only two optional parameters, a read-only annotation, and no output schema, the description is mostly complete for an agent to understand the tool's high-level purpose. It could be more complete by stating what the returned template contains or how the intelligent matching behaves, but nothing critical is missing for basic invocation.

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%, so the schema already documents both parameters adequately. The description adds modest semantic value by linking templateId to the 'by ID' mode and userRequest to the 'intelligent matching' mode, but it does not materially expand on the schema.

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 clearly states a specific verb ('Get') and resource ('workflow template'), and identifies two operation modes: by ID and by user requirements. It does not explicitly contrast with sibling tools like n8n_list_workflow_templates or n8n_search_public_templates, but the core purpose is unambiguous.

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 when to use each mode: provide templateId when the ID is known, otherwise provide userRequest for intelligent matching. However, it does not explain when to prefer this tool over the overlapping sibling n8n_search_public_templates or n8n_list_workflow_templates, so usage guidance remains implicit rather than explicit.

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