n8n_list_workflows

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context by warning that the response includes complete workflow data such as nodes and connections, which implies potentially large output. It does not discuss pagination behavior, but the read-only nature is already covered and the payload warning adds real value beyond annotations.

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 with zero filler. The core function is stated first, then the filters, then the critical warning and alternative. The warning is front-loaded where it can most influence tool selection.

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?

With no output schema and seven optional parameters, the description adequately conveys purpose, filters, and the important payload caveat. It lacks explicit mention of pagination or default result counts, but the schema covers parameter constraints and the description gives enough context for correct tool selection and invocation.

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%, so all seven parameters are already documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides, such as how filters combine or how cursor pagination works. Baseline 3 is appropriate.

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 ('List') and resource ('all workflows'), specifies that it returns full details, and lists the available filter dimensions. It actively distinguishes itself from the sibling tool n8n_list_workflows_summary by warning about the heavy payload, so an agent can tell them apart.

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 warning explicitly directs agents to n8n_list_workflows_summary when token efficiency matters, giving a clear alternative condition. However, it does not mention other relevant alternatives like n8n_get_workflow for fetching a single workflow, so the routing guidance is good but not exhaustive.

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