n8n_list_backups

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

No annotations provided, so description must carry behavioral info. 'List' implies read-only, but no explicit readOnlyHint or disclosure of side effects. The phrase 'before n8n mutations' adds some behavioral context but remains vague.

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 efficiently conveys core purpose. No unnecessary words. However, the phrase 'created before n8n mutations' could be clearer without being longer.

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?

Description adequately clarifies that this lists backups (restore points) rather than current workflows. But lacks details like output format or what qualifies as 'before mutations'. Simple tool but could be more 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 coverage is 100%, with each parameter well-described in the schema (limit, server_name, workflow_id). The description adds no further meaning to these parameters beyond the schema.

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?

Description clearly states 'List local workflow backups created before n8n mutations.' It specifies the verb (list), resource (workflow backups), and a qualifier, distinguishing it from siblings like n8n_list_workflows and n8n_restore_workflow. However, 'before n8n mutations' is slightly ambiguous.

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?

No guidance on when to use this tool versus alternatives like n8n_list_workflows or n8n_restore_workflow. The description implies a context (after mutations) but does not explicitly state when or when not to use it.

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