n8n_list_executions

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

The readOnlyHint annotation already establishes that this is a read-only operation. The description adds value by warning that includeData=true significantly increases token usage and recommending fields to reduce tokens, but it does not disclose pagination behavior, result shape, or any other execution-specific behavior beyond the filters.

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 short sentences with no filler. The core purpose and filters are stated first, followed by a useful, actionable tip about token usage. Every sentence earns its place.

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 read-only list operation with a fully documented parameter schema, the description covers the essential filters and adds token-usage guidance. It lacks explicit output-format or pagination details, but the cursor parameter and the simple 'list' semantics make this a minor gap rather than a blocking one.

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%, so every parameter is already documented in the schema. The description's tip about includeData=false and fields adds practical usage guidance but does not explain the parameters themselves beyond what the schema already provides.

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 a specific verb and resource ('List workflow executions') and enumerates the filterable dimensions (status, workflow ID, project). It does not explicitly differentiate itself from sibling n8n_get_execution, but the list-vs-get distinction is clear from the verb and resource name.

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 implies usage by stating what the tool lists and what filters are available, but it does not explicitly say when to prefer this over n8n_get_execution or related sibling tools. The guidance is adequate but relies on inference.

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