list_workflows

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination (despite having 'cursor' and 'limit' parameters), what the return value contains, or any side effects. The phrase 'List all' may be misleading given the optional pagination parameters.

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 extremely short (4 words), which could be considered concise, but it sacrifices necessary detail. It does not provide a structured explanation of the tool's functionality or parameters.

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?

Given the presence of two optional pagination parameters and no output schema, the description is inadequate. It does not specify what is returned (e.g., workflow IDs, full objects) or how pagination works, making it difficult for an agent to use the tool correctly.

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 0%, and the description does not explain the meaning or usage of 'limit' and 'cursor' parameters. These parameters suggest pagination, but the description fails to add that context, leaving the agent confused about how to use them.

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 clearly states the action (list) and resource (n8n workflows), matching the tool name. It is not a tautology and provides a basic understanding of the tool's purpose, though it does not differentiate from sibling tools like 'list_workflow_tags' or 'get_workflow'.

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 such as 'get_workflow' for a single workflow or 'list_executions' for other resources. The description does not specify prerequisites or context.

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