n8n_get_executions

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

With no annotations, the description must disclose behavior. It only says 'list recent executions' and 'can limit results', omitting details like the default limit, filtering by status/workflow_id (present in schema but not described), sorting, and the response structure. This is minimal for a tool with zero annotation support.

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 consists of two short sentences that are direct and free of redundant information. It front-loads the main purpose ('list recent executions') and mentions limit capability without fluff.

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 no output schema, so the description should explain the return value. It does not mention what data is returned for each execution, nor does it address pagination or the distinction from the singular execution retriever. The description leaves significant context unaddressed for a simple list tool.

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 covers 100% of parameters with descriptions, so baseline is 3. The description only adds that results can be limited, which is already evident from the 'limit' parameter description. No extra semantic meaning is provided beyond the schema.

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 explicitly states 'Listar ejecuciones recientes' (List recent executions), providing a clear verb and resource. It distinguishes from the singular n8n_get_execution by indicating a list of executions. However, it doesn't mention the filtering capabilities (status, workflow_id) which are key to its purpose.

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?

There is no explicit guidance on when to use this tool versus n8n_get_execution or n8n_stop_execution. The plural 'ejecuciones' and 'listar' imply its use case for retrieving multiple executions, but no alternatives or exclusions are mentioned.

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