get_execution_status

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'Fetches the status' without elaborating on what the status includes, possible error conditions, authentication requirements, or side effects. The description is too sparse to convey meaningful behavioral traits beyond being a read operation.

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 12-word sentence, front-loaded with the verb and resource. Every word contributes meaning, and there is no redundancy or fluff. It is appropriately sized for the tool's simplicity.

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 one-parameter tool, the description gives the core purpose but lacks an explicit link to execute_workflow's returned execution ID and does not describe the response structure (no output schema exists). It feels minimally complete but misses contextual details that would help an agent understand the full workflow.

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 has 0% description coverage, so the description must clarify parameters. It adds 'by id' to indicate that executionId is the identifier of the execution, which aligns with the parameter name but does not provide format, examples, or relationship to other tools. This is marginal added value over 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?

Description uses a specific verb 'Fetches' and a well-defined resource ('status of a previously triggered n8n execution by id'). It clearly distinguishes itself from sibling tools like list_workflows, get_workflow_schema, and execute_workflow by focusing on execution status retrieval.

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 'previously triggered' implies this tool is used after execute_workflow, but there is no explicit statement of when to use it versus alternatives or when not to use it. Sibling tool names provide context, but the description itself offers limited usage guidance.

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