n8n_export_all_workflows

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

Annotations already declare readOnlyHint=true, and the description adds that the tool reads all workflows and writes JSON files locally. It does not disclose directory creation behavior, overwrite semantics, or success/confirmation details, so it adds only modest behavioral context beyond the annotation.

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 two tight sentences with no filler. The action and output format are front-loaded, and the second sentence earns its place by clarifying the tool's relationship to snapshots.

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 tool with zero required parameters, one optional directory parameter, and read-only annotation, the description covers scope, destination, and relationship to existing backups. It does not explicitly describe return/confirmation behavior, but that is a minor gap given the low complexity and absent 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 100%, and the single directory parameter is already fully documented with its default path. The description's phrase 'local directory' aligns with the schema but adds no additional parameter-level meaning.

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 states a specific verb ('Back up'), resource ('every workflow of the instance'), and output form ('individual JSON files in a local directory'). It also distinguishes itself from per-change snapshots, making its purpose unambiguous even among many sibling tools.

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 gives clear context by positioning the tool as a full-instance safety net that complements per-change snapshots. It does not explicitly list alternatives or exclusions, but the intended use case is clear enough for an agent to decide when to invoke it.

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