n8n_get_workflow

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. The description adds critical behavioral details: the draft/publish model, that active mode returns running graph, and that it fails if no live version. No contradictions.

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, no wasted words. Front-loaded with main purpose and immediately followed by the key model distinction. Highly efficient.

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?

Explains all modes and key behaviors. Without an output schema, it covers what each mode returns. One minor gap: doesn't explicitly state that the response is a workflow object (but inferred). Otherwise complete.

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 already has 100% description coverage. The description goes further by explaining the draft vs active concept and what each mode returns beyond the schema's enum descriptions, e.g., 'active=published graph (errors if workflow has no live version)'.

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?

Clearly states 'Get workflow by ID' which is a specific verb+resource pairing. Distinguishes from sibling tools like create, delete, update, search by focusing on retrieval with detail levels.

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?

Explicitly explains the draft/publish model and lists each mode with its content, including that active mode errors if no live version. Provides clear context for choosing a mode, though no direct comparison to sibling tools.

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