list_workflows

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about pagination, result size, default limit, or ordering—all critical for a list endpoint with a 'limit' cap of 250. Only the API source is disclosed.

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?

A single, front-loaded sentence with no filler. It's concise but underwritten rather than optimally informative.

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?

A list tool with three undocumented parameters, no annotations, and no output schema needs substantially more guidance than one sentence. Nothing about return shape, pagination, or filtering semantics is provided.

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 0%, so the three parameters (limit, active, name_contains) have no documentation anywhere. The description mentions none of them, leaving the agent to guess whether 'name_contains' is a substring match or whether 'active' filters active-only or inactive-only.

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?

States a specific verb ('Lists') and resource ('workflows') and names the source (n8n API), so the agent knows this is a collection retrieval. It doesn't distinguish itself from siblings like get_workflow or get_workflow_by_name, though the plural 'list' vs singular 'get' implies scope difference.

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 when-to-use context, no mention of alternatives. The agent cannot tell from the description when to prefer list_workflows over get_workflow_by_name or get_workflow.

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