n8n-patterns-get

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

With no annotations available, the description carries full responsibility for behavioral disclosure. It indicates a read operation ('Get') but provides no details on side effects, authentication requirements, rate limits, or the exact structure of the returned JSON. The description is vague regarding the tool's behavior beyond the basic fetch.

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 extremely concise, consisting of two short sentences. The first sentence immediately states the purpose and action, and the second provides usage context. No unnecessary words or repetition.

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 the tool has one parameter, no output schema, and no annotations, the description is minimally adequate. It specifies the result is a 'full workflow JSON template' but does not describe its structure or potential error states. For a simple fetch operation, this may suffice, but it could be more complete by clarifying the template format or typical use.

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 schema provides 100% coverage for the single parameter ('workflow_id') with a clear description. The description adds the phrase 'by ID' which reinforces but does not add new meaning beyond what the schema already states. Thus, it meets the baseline but offers no additional semantic enrichment.

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 the action ('Get') and resource ('full workflow JSON template') and specifies retrieval by ID. It distinguishes from siblings like 'n8n-patterns-search' (which returns search results) and 'get-workflow' (which likely retrieves an existing workflow, not a template).

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 provides a clear use case ('fetch a template for deployment') but does not explicitly mention when to avoid using it or compare with alternatives. The sibling context implies this is for templates, while 'get-workflow' is for existing workflows, but the description doesn't articulate that distinction.

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