n8n_list_executions

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

No annotations are provided, so the description carries the full burden. It states the tool is read-only (listing executions) and lists return fields. It does not mention ordering (e.g., most recent first), authentication requirements, or pagination behavior beyond the limit parameter. For a simple list tool, this is adequate but lacks some context.

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, no wasted words. The first sentence covers purpose and return fields, the second provides a direct alternative. Extremely concise and well-structured.

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 no output schema, the description explicitly lists return fields. It covers the tool's core functionality and provides a clear alternative. Minor missing details like default sorting order, but overall sufficient for a simple list tool with well-documented parameters.

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%, with clear descriptions for all three parameters (workflowId, status, limit). The description adds no additional parameter information beyond what's in the schema, so it meets the baseline but does not exceed it.

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 verb 'List', the resource 'n8n executions', and the scope 'recent with optional filters'. It also specifies the exact fields returned (id, workflowId, workflowName, etc.), distinguishing it from sibling tools like n8n_get_execution and n8n_search_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 a clear alternative: 'Use n8n_get_execution for the full run log.' This helps the agent decide when to use this tool vs. a more detailed one. However, it does not explicitly mention when not to use it or compare with n8n_search_executions, leaving some ambiguity.

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