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. It effectively describes the tool's behavior: it enables automatic execution based on triggers, specifies prerequisites (automatic trigger nodes required), and clarifies limitations (manual-trigger workflows excluded). However, it lacks details on error handling, permissions, or side effects like rate limits.

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 front-loaded with the core purpose in the first sentence, followed by a crucial note in the second sentence. Both sentences earn their place by providing essential usage constraints without redundancy or fluff, making it highly efficient and well-structured.

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?

Given the tool's moderate complexity (activation operation with prerequisites), no annotations, and no output schema, the description is largely complete. It covers purpose, usage guidelines, and behavioral aspects, but could benefit from mentioning response format or error cases to be fully comprehensive for an agent.

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 description coverage is 100%, with the input schema fully documenting the 'id' parameter. The description adds minimal semantic value beyond the schema, only implying the ID is for a workflow without providing additional context like format or validation rules. This meets the baseline for high 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 clearly states the specific action ('Activates'), the resource ('a workflow'), and the mechanism ('by its ID'), distinguishing it from siblings like deactivate_workflow or get_workflow. It explicitly mentions enabling automatic execution based on triggers, which clarifies its functional scope beyond just a state change.

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 provides explicit guidance on when to use this tool ('workflows with automatic trigger nodes') and when not to use it ('workflows with only manual triggers cannot be activated'). It also implicitly contrasts with deactivate_workflow by specifying activation, offering clear usage context.

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

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

With no annotations, the description carries full burden and discloses key behavioral traits: it explains activation constraints (automatic vs. manual triggers), mentions the return value (created workflow with ID), and implies it's a write operation. It doesn't cover error handling or permissions.

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?

Two sentences with zero waste: first states purpose and key constraint, second specifies return value. It's front-loaded with essential information and appropriately sized.

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 creation tool with no annotations and no output schema, the description is fairly complete: it covers purpose, activation behavior, and return value. However, it lacks details on error cases or permissions, which could be useful given the complexity.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond schema by mentioning 'nodes and connections' and activation note, but doesn't provide additional syntax or format details. Baseline 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 clearly states the verb 'creates' and resource 'new workflow in n8n', specifying it includes 'nodes and connections'. It distinguishes from siblings like update_workflow (modifies existing) and list_workflows (reads).

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?

It provides clear context about when activation works (only for workflows with automatic triggers) and implies usage for creation vs. alternatives like update_workflow. However, it doesn't explicitly state when not to use it or compare with all siblings.

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

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

With no annotations provided, the description carries full burden and does well: it discloses the tool's effect (workflow stops running automatically but remains accessible), reversibility (can be reactivated later), and persistence (still exists for manual execution). It doesn't mention permissions or error conditions, but covers key behavioral aspects.

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?

Two sentences, front-loaded with the core purpose, followed by important behavioral context and usage guidance. Every sentence adds value with zero waste, making it highly efficient.

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 mutation tool with no annotations and no output schema, the description provides good context: it explains the action, outcome, and when to use it. It could mention error cases or return values, but covers the essentials well given the complexity.

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 description coverage is 100%, so the schema already documents the 'id' parameter fully. The description adds no additional parameter details beyond what's in the schema, meeting the baseline for high 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 clearly states the specific action ('deactivates'), target resource ('workflow'), and mechanism ('by its ID'), distinguishing it from siblings like delete_workflow. It explains the effect ('preventing it from running automatically') and contrasts with deletion.

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?

It explicitly states when to use this tool ('instead of deleting workflows that you might need again') and implies when not to use it (if permanent removal is needed, use delete_workflow). This provides clear guidance relative to alternatives.

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

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. It effectively communicates critical behavioral traits: the action is permanent and irreversible ('cannot be undone'), and it suggests caution. However, it doesn't mention potential side effects like cascading deletions or permission requirements.

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 perfectly front-loaded with the core purpose in the first sentence, followed by crucial warnings and alternatives. Every sentence earns its place with no wasted words, making it highly efficient and scannable.

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 destructive tool with no annotations and no output schema, the description does an excellent job covering the most critical aspects: purpose, irreversible nature, and alternatives. It could be more complete by mentioning what happens to associated executions or data, but given the context, it's substantially helpful.

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 description coverage is 100%, with the single parameter 'id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema, so it meets the baseline expectation for high 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 clearly states the specific action ('permanently deletes') and resource ('a workflow by its ID'), distinguishing it from siblings like deactivate_workflow and update_workflow. It uses precise language that leaves no ambiguity about the tool's function.

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 provides explicit guidance on when to use this tool ('permanently deletes') versus alternatives ('consider deactivating workflows instead if you might need them again later'). It clearly warns about irreversible consequences and suggests a safer alternative when appropriate.

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

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves information (implying read-only) and mentions potential data size issues ('may be large for complex workflows'), adding some behavioral context. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a mutation-heavy 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?

The description is front-loaded with the core purpose, followed by specific use cases. Both sentences earn their place by adding clarity and context without redundancy, making it efficient and well-structured.

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?

Given no annotations and no output schema, the description provides adequate purpose and usage guidance but lacks details on return values, error cases, or system constraints. For a tool with 3 parameters and in a workflow execution context, it is minimally viable but has clear gaps in behavioral transparency.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by implying the 'includeData' parameter's impact on debugging, but it does not provide additional syntax or format details. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('retrieves') and resource ('detailed information about a specific workflow execution'), specifying what it does. It distinguishes from siblings like 'list_executions' by focusing on a single execution and mentioning debugging use cases, making it specific and differentiated.

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 provides clear context on when to use it ('Particularly useful for debugging failed workflows or understanding data transformations between nodes'), which helps differentiate from tools like 'list_executions'. However, it does not explicitly state when not to use it or name specific alternatives, keeping it at a 4.

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

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves details (implying a read-only operation) and mentions output verbosity levels, which adds useful context. However, it lacks details on permissions, error handling, or response format, leaving behavioral gaps for a tool with no annotation coverage.

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 front-loaded with the core purpose in the first sentence and follows with usage guidance in the second. Both sentences earn their place by adding clarity and context without redundancy, making it efficiently structured and appropriately sized for the tool's complexity.

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?

Given no annotations and no output schema, the description does well by explaining the tool's purpose, usage, and implied parameters. It covers key aspects like what is retrieved and when to use it, but lacks details on return values or error cases, which could be more complete for a retrieval tool with no structured output information.

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 description coverage is 100%, so the schema already documents both parameters (id and verbosity) thoroughly. The description adds minimal value beyond the schema by implying the id is used to retrieve workflow details, but it doesn't provide additional syntax or format details. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('Retrieves') and resource ('complete details of a specific workflow by its ID'), specifying what it returns ('including all nodes, connections, settings, and metadata'). It distinguishes from siblings like list_workflows (which lists workflows) and get_execution (which retrieves execution details), making the purpose specific and well-differentiated.

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 explicitly states when to use this tool ('when you need to examine a workflow's structure before updating it or to understand how it works'), providing clear context. It implies alternatives by mentioning list_workflows for obtaining IDs and update_workflow for updates, giving practical guidance on usage scenarios.

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

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. It effectively communicates that this is a read-only operation (implied by 'Lists') and adds practical context about error prevention, but does not detail aspects like rate limits, authentication needs, or pagination behavior, which are relevant for a list tool.

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 front-loaded with the core purpose in the first sentence, followed by practical usage guidance, with no redundant or verbose language. Every sentence adds value, making it efficient and well-structured for quick comprehension.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is largely complete for a read-only list operation, covering purpose, usage context, and error prevention. However, it lacks details on output format or behavioral traits like pagination, which could enhance completeness.

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 description coverage is 100%, so the schema already fully documents both parameters (category and verbosity). The description does not add any parameter-specific information beyond what the schema provides, such as examples or usage tips, meeting the baseline for high 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 clearly states the specific action ('Lists all available nodes') and resource ('in the n8n instance'), with explicit differentiation from siblings like create_workflow or update_workflow by focusing on node discovery rather than workflow operations. It goes beyond the tool name by explaining the scope and 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?

The description provides explicit guidance on when to use this tool ('BEFORE creating or updating workflows') and why ('to ensure you only use valid node types... prevent errors'), with clear context for its application relative to other workflow-related tools. It effectively distinguishes its role in the toolset.

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

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

No annotations are provided, so the description carries the full burden. It discloses that the tool lists 'history with details' and mentions filtering capabilities, but lacks information on permissions, rate limits, pagination, or response format. For a read-only tool with no annotations, this is adequate but leaves behavioral gaps.

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 appropriately sized and front-loaded, with the core purpose stated first. Every sentence adds value: the first defines the tool, the second gives usage guidelines, and the third explains filtering options. There is no wasted text.

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?

Given the tool's complexity (4 parameters, no output schema, no annotations), the description is complete enough for basic use but lacks details on output structure, error handling, or advanced behavioral traits. It covers purpose and filtering but doesn't fully compensate for the absence of annotations and output schema.

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 description coverage is 100%, so the schema fully documents all 4 parameters. The description adds marginal value by mentioning filtering by 'workflow ID, status, and limited to a specific number,' which aligns with the schema but doesn't provide additional syntax or format details beyond what's already in the schema descriptions.

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 clearly states the tool's purpose with specific verbs ('Lists workflow execution history') and resources ('workflow execution'), distinguishing it from siblings like 'get_execution' (singular) or 'list_workflows' (different resource). It specifies the details included: 'success/failure status, duration, and timestamps'.

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 provides clear context for when to use this tool: 'to monitor workflow performance, troubleshoot issues, or verify that workflows are running as expected.' It does not explicitly state when not to use it or name alternatives, but it implies usage for historical data rather than single executions (vs. 'get_execution').

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

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

With no annotations provided, the description carries full burden. It discloses that this is a listing operation with filtering capabilities and mentions output verbosity levels, which adds useful context. However, it doesn't cover important behavioral aspects like pagination, rate limits, authentication requirements, or error handling for a tool with 4 parameters.

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 efficiently structured in two sentences: the first states purpose and output, the second provides usage guidance and filtering capabilities. Every element earns its place with no redundant information.

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 listing tool with 4 parameters, 100% schema coverage, but no annotations or output schema, the description provides adequate purpose and usage context. However, it lacks details about return format, pagination behavior, or error scenarios that would be helpful given the filtering complexity.

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 description coverage is 100%, so the schema already documents all 4 parameters thoroughly. The description mentions filtering capabilities ('Results can be filtered by active status, tags, or name') which aligns with the schema but doesn't add significant semantic value beyond what's already in the parameter descriptions.

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 clearly states the verb ('Lists') and resource ('all workflows from n8n') with specific output details ('basic information including ID, name, status, creation date, and tags'). It distinguishes from siblings like 'get_workflow' (specific workflow) and 'list_executions' (different resource).

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 provides explicit context for when to use this tool ('to get an overview of available workflows before performing operations on specific workflows'), which helps differentiate from siblings like 'get_workflow'. However, it doesn't explicitly state when NOT to use it or name specific alternatives for filtering scenarios.

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

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: it's a mutation operation (implied by 'Updates'), requires the 'entire workflow structure' (not partial updates), and has a prerequisite relationship with get_workflow. However, it doesn't cover permissions, error handling, or what happens to existing executions, leaving some gaps.

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 perfectly concise with three sentences that each earn their place: first states the core purpose, second provides usage context, third clarifies a critical behavioral constraint. No wasted words, and the most important information (full-structure requirement) is appropriately emphasized at the end.

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 mutation tool with no annotations and no output schema, the description does well by explaining the update process, prerequisite relationship with get_workflow, and the full-structure requirement. It covers the essential context for proper use. The main gap is lack of information about what the tool returns or error conditions, but given the schema coverage and clear purpose, it's reasonably complete.

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 description coverage is 100%, so the schema already fully documents both parameters (id and workflow). The description adds minimal value beyond the schema by emphasizing that the workflow parameter must be 'complete' and 'not just the parts being changed', but this is essentially restating what's in the schema description for the workflow property. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the specific action ('Updates an existing workflow') and resource ('workflow'), distinguishing it from siblings like create_workflow (creation) and delete_workflow (deletion). It specifies the scope of updating 'with new configuration', making the purpose unambiguous.

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 provides explicit context for when to use this tool: 'Typically used after retrieving a workflow with get_workflow, modifying its structure, and then saving the changes.' This gives clear guidance on the workflow process. However, it doesn't explicitly state when NOT to use it or mention alternatives like create_workflow for new workflows.

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