n8n: List executions

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds that it returns execution history. However it says nothing about pagination behavior despite limit/cursor parameters, and it advertises filtering "by date" when no date parameter exists in the schema, which is misleading.

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?

Three short sentences with the core purpose front-loaded and no filler. The bracketed "[UNIFIED]" tag and the trailing optionality note are the only low-value bits.

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?

For a 7-parameter listing tool with zero schema descriptions and no output schema, the description should at minimum explain site scoping, pagination via limit/cursor, and include_data. None of these are addressed, leaving an agent to guess at most of the call surface.

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% across 7 parameters, so the description must carry parameter meaning and largely does not: it names status and workflow but omits site, limit, cursor, project_id, and include_data entirely. It also references a date filter that the schema does not define.

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 gives a specific verb and resource ("List workflow executions") plus the filter dimensions, so an agent can tell this apart from write-side siblings like n8n_delete_executions. The "[UNIFIED]" prefix is unexplained jargon and does not add differentiation.

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?

It notes that "All filter parameters are OPTIONAL," which hints at how to call it, but there is no when-to-use guidance, no mention of when a different listing tool or a single-execution fetch is preferable, and no prerequisites (e.g. site scoping or permissions).

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