Get execution

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

Beyond annotations, reveals that includeData triggers a request to n8n but the MCP still withholds all payload data, and specifies the returned fields (identity, status, timing, retry, dataPolicy). Adds meaningful behavioral context.

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 dense sentences, front-loaded with the action, and no filler. Every clause adds value.

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?

Complete for a simple 2-param read tool: purpose, permission, ID semantics, return shape, and data access limitations are all covered. Output schema exists and is not contradicted.

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?

Even with 100% schema coverage, the description clarifies that executionId is the list-based record ID (not workflowId) and explains the true behavior of includeData, which the schema only partially captures. Adds significant 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?

States clearly it gets metadata for a single execution, and explicitly distinguishes executionId from workflowId. Differentiates from the list sibling by saying 'Use list for discovery.' Verb+resource is precise.

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?

Gives explicit alternative ('Use list for discovery') and notes the permission requirement. Also implies when not to use (for payload data) by explaining includeData still withholds node inputs/outputs.

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