List executions on a live n8n instance

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

With no annotations, the description carries the full burden of behavioral disclosure. 'List recent workflow executions' implies a read-only operation but gives no details about pagination (cursor/limit), default ordering, supported filters (status, projectId, workflowId), or return format, which are critical for an agent to invoke it safely and effectively.

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 concise and front-loaded with the core action, but it is under-specified. It has no additional structure or elaboration, making it minimally viable without being 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?

Given five parameters, no annotations, and no output schema, the description is incomplete. It does not address pagination, filtering options, or the expected response structure, which are necessary for an agent to confidently use this tool in a workflow.

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?

The schema has 5 parameters with 0% description coverage, and the description mentions none of them. It fails to explain how limit, cursor, status, projectId, or workflowId affect results, leaving the agent without any semantic context for these fields beyond their names.

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 uses the specific verb 'List' and identifies the resource as 'recent workflow executions,' which clearly conveys a collection-level read operation. This distinguishes it from sibling tools like n8n_get_execution (single execution) and n8n_delete_execution (mutation), though it omits the n8n instance context present in the title.

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 is provided on when to use this tool versus alternatives. It does not mention that n8n_get_execution is for fetching a single execution, nor does it discuss use cases like monitoring or debugging, leaving usage entirely to inference.

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