n8n_get_execution

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'obtiene' (gets) implies a read-only operation, which is a useful behavioral trait. However, it does not mention authentication requirements (beyond the api_key parameter), error behavior if the execution is not found, or response format. These are gaps, but the read-only implication is conveyed.

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 a single, focused sentence with no filler content. It front-loads the action and provides the essential scope ('by its ID'). Every word earns its place, and there is zero waste.

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?

This is a simple get-by-ID tool with no output schema. The description states what it does but gives no indication of the returned data structure, error handling, or the need for a base_url parameter. While the tool is simple, the lack of output schema and undocumented base_url create ambiguity for an agent invoking it. The description is adequate but not rich.

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 input schema provides descriptions for 'id' and 'api_key' (67% coverage), but 'base_url' is undocumented. The tool description adds no parameter details beyond what the schema already states. It does not clarify the purpose of 'base_url' or any expected formats, so the description does not compensate for the missing schema coverage.

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 ('obtiene' = gets) and identifies the exact resource ('el detalle de una ejecución' = execution detail) with the required key ('por su ID' = by its ID). It clearly distinguishes this tool from siblings like n8n_list_executions (which lists executions) and n8n_get_workflow (which gets a workflow).

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 phrase 'por su ID' clearly indicates this tool is used when you have a specific execution ID and need its detail. It does not explicitly mention alternatives (e.g., use n8n_list_executions to find IDs), but the context is clear and no exclusions are stated. This is sufficient for a simple get-by-ID tool.

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