Fetch a single workflow by ID

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

Description adds that it returns full nodes/connections payload and pairs with workflow.lint, beyond annotations (readOnly, idempotent, non-destructive). No contradictions; could mention timeout or auth failure handling.

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 sentences, front-loaded with purpose and requirements. Each sentence adds value: first gives core function and environment, second details return type and suggested pairing.

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?

With output schema present and a single well-documented parameter, the description sufficiently covers behavior. Full context given for a simple retrieval tool.

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 covers 100% of parameters with clear description for 'id'. Description mentions 'by id' but adds no extra semantic meaning beyond what schema provides. Baseline 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?

Description clearly states it fetches a single workflow by ID, a specific verb+resource pair. Distinguishes from siblings like workflow.list (listing) and workflow.lint (auditing) by mentioning pairing with lint.

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?

Specifies environment prerequisites (N8N_API_URL + N8N_API_KEY) and suggests a use case (pair with workflow.lint). No explicit when-not, but context with siblings implies it's for fetching one workflow by ID.

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