n8n_get_execution

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

readOnlyHint=true already communicates that this is a safe read operation, and the description's 'Get' is consistent with that annotation. The description adds little behavioral context beyond the word 'detailed', so this is minimally transparent but not contraddictory.

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?

It is a single, front-loaded sentence that states the action and target immediately. There is no redundant wording or filler.

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 simple read-only getter with one required parameter and one boolean flag, the description plus the schema is mostly sufficient. It could be slightly more explicit about what 'detailed information' includes or when to choose node-level execution data instead, but no essential calling detail is missing.

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 schema provides complete descriptions for both parameters (id: 'Execution ID', includeData: 'Include execution data'), and the description itself adds no further parameter semantics. With 100% schema coverage, the baseline score of 3 is appropriate.

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 clear action verb ('Get') with a concrete resource ('a specific execution') and says the result is detailed information. This distinguishes it from list, delete, and retry execution tools, so an agent can identify the right sibling without inspecting schemas.

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 this tool is for when an agent has an execution ID and wants more detail than a list view would give. However, it does not explicitly contrast it with siblings like n8n_list_executions or n8n_get_node_execution_data, and there is no when-not guidance.

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