Get a workflow from a live n8n instance

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

No annotations are provided, so the description must disclose behavioral traits. 'Fetch' implies a read-only operation, but there is no explicit statement about safety, permissions, or side effects. It doesn't add any behavioral context beyond the verb itself.

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 a single sentence, front-loaded with the verb and resource, with no wasted words. It's optimally concise and structured.

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 fetch-by-id tool, the description covers the core purpose and even mentions 'full definition' to hint at the return value. However, it omits the behavior of excludePinnedData and provides no details about response structure or error cases, which is a notable gap given 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 0%, so the description must compensate. It clarifies the 'id' parameter via 'by id', but completely ignores 'excludePinnedData'. Without explanation, the agent cannot know what that parameter does or when to set it.

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 identifies the action ('Fetch'), the resource ('one workflow'), and the scope ('full definition by id'). It effectively distinguishes this from sibling tools like n8n_list_workflows (listing) and n8n_get_execution (executions).

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 the usage context: when you need a single workflow's full definition by ID. It doesn't explicitly state alternatives or exclusions, but the clear verb and resource make the intended use obvious. A slight deduction for not mentioning what to use for listing workflows.

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