n8n_get_workflow

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

No annotations provided, so description must carry burden. It states the tool 'Get detailed information' which implies a read operation with no side effects. It does not mention potential errors (e.g., invalid ID), authentication requirements, or performance characteristics (e.g., latency for large workflows). However, the core behavior is clear.

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?

Single sentence that is front-loaded with the core purpose ('Get detailed information') and specifies the resource and scope. No superfluous words. Efficiently conveys the tool's function.

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's simplicity (two parameters, no output schema, no annotations), the description covers the main functionality. It does not explain return format or error behavior, but for a straightforward read tool, this is adequate. Missing info like 'workflow_id format' could improve completeness.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining the output includes 'all nodes, connections, and settings', which gives context beyond the raw schema. However, it does not elaborate on the format of 'workflow_id' (e.g., URL or just ID) or the default server behavior.

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 uses specific verb 'Get' and resource 'n8n workflow', and includes details about what is retrieved ('all nodes, connections, and settings'). It clearly distinguishes from sibling tools like n8n_list_workflows (list vs. detail) and n8n_export_workflow (export format vs. raw details).

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 use when needing detailed workflow information, but does not explicitly state when not to use or alternatives. However, the sibling context helps differentiate, and the description makes clear it returns full details, not just a list or export.

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