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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write-to-external-system profile is covered. The description adds real value with the permission requirement for activate and the 'unmodified' constraint, but says nothing about what happens on partial failures, whether redeploying a template duplicates a workflow, or what is returned.

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?

Front-loaded single sentence carries the core behavior and the routing hint; the arg list is short and each entry earns its place. The docstring-style indentation is a minor formatting artifact rather than wasted 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?

Covers the deploy-vs-adapt decision, parameter sourcing, and the activate permission for a 3-param, 0%-coverage schema with no output schema. Missing is any statement of what the call yields (workflow ID/handle) or whether deployment targets a new workflow, which matters for chaining to set_workflow_active or trigger_execution.

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 0%, so the description carries the burden and mostly does: template_id is sourced from search_templates, template_url is flagged as a legacy alias, and activate is tied to a permission. It omits which field wins when both template_id and template_url are supplied, or whether template_url accepts a full URL versus an ID.

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?

Specific verb plus resource: deploy a verified template into the user's n8n, explicitly scoped as 'unmodified'. It also distinguishes itself from get_template and save_workflow, so an agent can separate deployment from adaptation without opening a schema.

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?

States the exclusion condition and the alternative route: 'use get_template + save_workflow to adapt it first'. The template_id arg also points at search_templates as the discovery step, giving a complete routing chain.

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