List workflows on a live n8n instance

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

With no annotations present, the description carries the full burden of behavioral disclosure. It says only 'List workflows,' which implies a read-only operation but does not disclose pagination behavior, rate limits, or what data is returned. This is minimal disclosure for a live API tool.

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 a single clear sentence with no filler, making it concise and front-loaded. However, its brevity is a double-edged sword: it is not verbose, but it omits important details, which is captured in the completeness dimension.

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 tool's complexity (6 optional parameters, no output schema, no annotations), the description is severely inadequate. It provides no information about input semantics, return value structure, pagination, or edge cases, making it nearly impossible for an agent to invoke 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 coverage is only 17% (only 'tags' has a description), yet the description adds no parameter information. It fails to explain name, tags, limit, active, cursor, or projectId, leaving the agent without any semantic understanding of the six optional parameters.

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 tool lists workflows from the connected n8n instance, using a specific verb ('List') and resource ('workflows'). It distinguishes from sibling tools like get, create, update, and delete workflows, though it doesn't explicitly contrast with list_executions.

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 provides no guidance on when to use this tool versus alternatives such as n8n_get_workflow or search_nodes. The only context given is 'connected n8n instance,' which specifies the environment but not the conditions or scenarios for use.

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