n8n_list_workflow_snapshots

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

The readOnlyHint annotation already marks this as safe/read-only, and the description is consistent with that. It adds valuable behavioral context by explaining that snapshots are local to this server and are saved automatically before mutations, which clarifies what data can be expected and why.

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 concise sentences with no filler. The action is front-loaded, and the second sentence earns its place by explaining snapshot creation behavior. Every word adds value.

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 single-parameter, read-only tool, the description plus schema and annotations are largely sufficient. The main gap is the lack of an output schema or any mention of what fields the returned snapshots contain, but for simply listing snapshots of a workflow this is a minor omission.

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?

The schema has 100% description coverage for the single `id` parameter ('Workflow ID'), so the description does not need to add much. It merely reinforces that the parameter identifies a workflow. This meets the baseline but does not exceed it.

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 clear action and resource: 'List local snapshots of a workflow.' This is specific and easily distinguishable from diff/rollback operations by the verb. It does not explicitly name sibling tools to differentiate itself, but the scope ('local') adds helpful clarity.

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 useful context about when snaps shots are created—automatically before every update, partial update, or delete—so an agent knows snaps shots should exist after such operations. However, it does not explicitly say when to choose this tool over related tools like n8n_rollback_workflow or n8n_diff_workflow_snapshot.

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