n8n_backup_workflow

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

With no annotations, the description carries the full burden and does well: it discloses that nothing is written to n8n, that the backup is read back and checksum-verified, and that a downstream tool enforces its presence. It omits storage location, naming/overwrite behavior, and failure modes, which keeps it from a 5.

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?

Three short sentences, each load-bearing: what it does, the safety guarantee, and the verification/dependency contract. Front-loaded with the core action and no filler.

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 one-parameter tool with no output schema and no annotations, the description covers purpose, side-effect profile, verification, and inter-tool dependency. It does not say what the call returns (backup id, path, or checksum), which is the main remaining gap since no output schema exists.

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?

One parameter with 0% schema description coverage, but workflow_id is self-explanatory and the description's 'any n8n workflow' implicitly confirms it accepts an arbitrary workflow identifier. No additional format or constraint details are offered beyond the schema's minLength.

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?

States a specific verb and resource ('Save a verified local backup of any n8n workflow') with an added qualifier (verified, local) that separates it from siblings like n8n_get_workflow and n8n_diff_workflow. An agent can tell immediately this creates a durable artifact rather than reading or comparing workflows.

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?

Gives clear context for use by tying it to n8n_apply_workflow_update: the backup is a prerequisite that must match the exact version being changed. It lacks explicit when-not guidance (e.g. no need for a backup on read-only operations), so it stops short of a 5.

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