List executions

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses crucial behavior: 'never auto-paginates,' 'includeData only reports whether data exists—values remain withheld,' and 'returns metadata and nextCursor.' This adds meaningful context about pagination limits and data privacy that annotations alone do not convey.

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 sentences, each with a distinct purpose: purpose/scope, usage guidance, and behavioral/security constraints. No redundant or filler words; the description is dense yet readable and front-loaded with the most important info.

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?

The tool has an output schema, so return values are documented there. The description covers permission requirements, pagination behavior, and the nuance that data values are withheld even when includeData is true. Given the tool's simplicity and strong annotations/schema coverage, this description fully equips an agent to use it correctly.

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?

Although the schema already provides 100% parameter descriptions, the description adds semantic depth: 'status and workflowId filter upstream' clarifies server-side filtering, 'cursor resumes one prior page' explains the cursor's single-step behavior, and 'includeData only reports whether data exists' explicitly resolves the parameter's meaning beyond its schema text. This is valuable added meaning.

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 opens with a specific verb and resource: 'List one Public API page of saved execution metadata.' It clearly distinguishes the tool from its sibling by noting 'use n8n_executions_get when an ID is known,' which positions this as the discovery/triage tool.

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?

Explicit guidance is given: 'Use it for discovery and bounded triage; use n8n_executions_get when an ID is known.' It also states the required permission ('Requires execution-list permission') and pagination behavior ('never auto-paginates'), leaving no ambiguity about when and how to use it.

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