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

No annotations are provided, so description carries full burden. It states the tool can both activate and deactivate (consistent with the 'active' parameter), but it does not disclose effects like whether deactivation loses state or stops executions, or what happens if the workflow is already in the requested state. Expected behavior around idempotency or side effects is missing.

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?

Single sentence with 7 words. No filler. Every word earns its place, though it could include more usage guidance without losing conciseness.

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 3 simple parameters and no output schema, the description is nearly complete for a straightforward toggle action. Missing behavioral transparency (what happens on toggle, idempotency) and usage guidelines, but still sufficient for basic invocation. The list of sibling tools is available for context but not leveraged.

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 baseline is 3. However, the description explicitly ties the 'active' boolean to activation/deactivation, which reinforces the schema description and adds slight value. The 'server_name' default behavior is noted. No extra details on workflow_id format or validation, but adequate given 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?

Description uses 'activate or deactivate' as verb with 'n8n workflow' as resource, which is specific and distinguishes from siblings like n8n_create_workflow, n8n_delete_workflow, or n8n_update_workflow. It clearly conveys the two-state toggle nature of the tool.

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?

Description lacks explicit when-to-use or when-not-to-use guidance. It does not mention that activation requires a workflow to exist and be valid, nor does it contrast with related tools like n8n_create_workflow (for creation) or n8n_update_workflow (for non-status changes). Usage context is only implicit.

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 must cover behavioral aspects. It discloses the action (add or update) and the parameter dependencies, but does not mention side effects (e.g., whether updating a server breaks existing workflows) or authentication requirements beyond the key.

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 two sentences with no filler. It front-loads the purpose and provides a practical tip. Every word earns its place.

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 simplicity of the tool (4 params, no output schema), the description is sufficient. It covers the main use case and required parameters. Minor gap: no mention of validation or error cases.

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 coverage is 100%, so baseline is 3. The description adds value by explaining where to get the API key (Settings > API), which goes beyond the schema's description. However, it does not elaborate on 'is_default' behavior.

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 adds or updates an n8n server connection, distinguishing it from sibling tools like n8n_remove_server or n8n_ping_server. The verb 'add or update' and resource 'n8n server connection' are specific.

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 includes a helpful hint about API key creation location, but does not explicitly state when to use this tool over siblings (e.g., for initial setup vs. updating existing server) or provide exclusion criteria.

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 provided, so description must carry full burden. Notes that server_name uses default if omitted, and activate is optional. However, lacks details on idempotency, partial failures, or whether nodes must be valid n8n nodes.

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?

Very concise, two sentences. Front-loaded with purpose. Could include a brief note on usage context without adding much length.

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?

No output schema, so description should hint at return value (e.g., 'Returns the created workflow'). Lacks this. Adequate given moderate complexity and sibling tools that cover other operations.

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 coverage is 100%, so baseline is 3. Description adds no extra context beyond schema; doesn't explain relationships between parameters (e.g., connections must reference node names) or constraints on node types.

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?

Clearly states 'Create a new n8n workflow' with the verb 'Create' and resource 'n8n workflow'. Distinguishes from sibling tools like n8n_import_workflow (imports from file) and n8n_update_workflow (modifies existing).

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?

No explicit guidance on when to use this tool versus alternatives like n8n_import_workflow or n8n_update_workflow. The description implies it's for new workflows, but doesn't exclude cases where import might be better.

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?

The description explicitly states 'This action cannot be undone', which is a critical behavioral trait. Given no annotations, this provides key information about irreversibility, but could be enhanced by noting any side effects like cascading deletion of executions.

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?

Extremely concise: two sentences that clearly state purpose and a critical behavioral note. No wasted words.

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 two simple parameters (workflow_id and server_name) and no output schema, the description is mostly adequate for a deletion operation. However, it lacks explanation about success/failure responses or error handling, which an agent might need.

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?

With 100% schema description coverage, the schema already defines the two parameters well. The description doesn't add extra parameter meaning but is not expected to since schema is comprehensive.

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 states 'Delete a workflow from an n8n server', which is a clear verb-resource pairing. However, it doesn't differentiate sibling tools like n8n_remove_server or n8n_deactivate_workflow, though the distinction is somewhat implied by the verb 'delete'.

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 irreversible deletion, but lacks explicit guidance on when to use it vs alternatives like deactivating a workflow. No exclusion criteria or prerequisites are mentioned.

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 burden. It describes a read-only retrieval operation, but does not mention if there are rate limits, pagination, or other behavioral details. A 3 is appropriate as it is not misleading but lacks depth.

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 short sentences, no wasted words. Front-loaded with purpose, then use case. Efficient and direct.

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 is simple (1 optional param, no output schema), the description covers the essentials. However, it does not describe what the returned information looks like or any details about common node types, leaving some ambiguity.

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 coverage is 100% with one parameter, and the description adds context by mentioning the parameter filters by category. The description adds value by explaining that the tool is for discovering which nodes to use, beyond what the schema (which just lists options) provides.

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 retrieves information about n8n node types and its purpose is understanding which nodes to use. The verb 'Get information' and resource 'common n8n node types' are specific, though it doesn't distinguish from siblings beyond the scope.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies it's for choosing nodes in workflows, but no when-not-to-use or alternative tool comparisons are given.

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 burden. It states the tool is read-only (exporting), but does not disclose any error behaviors, authentication requirements, or rate limits. The description is accurate but minimal in disclosing behavioral traits beyond the obvious.

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 concise at two sentences. It front-loads the core purpose and adds a brief statement about the return value. No wasted words.

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 output schema, the description does explain return format (JSON, importable workflow definition). But it lacks details like what happens if the workflow ID doesn't exist, or if the server is unreachable. For a simple export tool, it's mostly adequate but not exhaustive.

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 coverage is 100%, so the schema already documents both parameters. The description does not add additional semantics beyond what the schema provides, so 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 tool exports a workflow from n8n as JSON, returns the complete workflow definition for import into another instance. It uses specific verb 'Export', specific resource 'workflow', and output format 'JSON', which distinguishes it from siblings like n8n_get_workflow (which likely returns a different representation) and n8n_import_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 description implies usage for exporting workflows and mentions the output is intended for import into another n8n instance, but does not explicitly state when to use this tool versus alternatives like n8n_get_workflow, nor does it mention prerequisites or limitations (e.g., needing the server to be connected).

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 provided, so description must carry burden. It states the tool 'Get detailed information' which implies a read operation with no side effects. It does not mention potential errors (e.g., invalid ID), authentication requirements, or performance characteristics (e.g., latency for large workflows). However, the core behavior is clear.

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?

Single sentence that is front-loaded with the core purpose ('Get detailed information') and specifies the resource and scope. No superfluous words. Efficiently conveys the tool's function.

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 simplicity (two parameters, no output schema, no annotations), the description covers the main functionality. It does not explain return format or error behavior, but for a straightforward read tool, this is adequate. Missing info like 'workflow_id format' could improve 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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining the output includes 'all nodes, connections, and settings', which gives context beyond the raw schema. However, it does not elaborate on the format of 'workflow_id' (e.g., URL or just ID) or the default server behavior.

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 specific verb 'Get' and resource 'n8n workflow', and includes details about what is retrieved ('all nodes, connections, and settings'). It clearly distinguishes from sibling tools like n8n_list_workflows (list vs. detail) and n8n_export_workflow (export format vs. raw details).

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 use when needing detailed workflow information, but does not explicitly state when not to use or alternatives. However, the sibling context helps differentiate, and the description makes clear it returns full details, not just a list or export.

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 only states that the tool creates a workflow on the server. It does not disclose whether the import is idempotent, what happens if the workflow already exists, or any side effects (e.g., replacing existing workflow? duplicates?). Given the lack of annotations, more behavioral detail would be helpful, but the description is not misleading.

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 two sentences, front-loaded with the primary purpose. Every sentence adds value: first states the action and resource, second clarifies input and server context. No unnecessary words.

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 has a clear input schema (100% coverage) and no output schema, the description adequately explains what the tool does. It does not detail the return value (which is acceptable since no output schema exists), but it could mention whether the imported workflow's ID or status is returned. However, for a simple import tool with three parameters, the description is mostly 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 documents all three parameters. The description adds minimal value beyond what the schema provides, but it does clarify that the tool expects a 'full n8n workflow JSON' and that server_name defaults if omitted. The purpose of the activate parameter is clear from the schema. A score of 4 is appropriate because the schema does the heavy lifting, but the description adds useful context about the JSON being 'full' and the default behavior of server_name.

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 ('import') and resource ('workflow JSON onto an n8n server'), and explicitly mentions creating the workflow on the server. It sufficiently distinguishes from sibling tools like n8n_create_workflow (which may imply a different creation method) and n8n_export_workflow (the reverse operation).

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 used when you have a full n8n workflow JSON and want to create it on the server. However, it does not differentiate from n8n_create_workflow (could be a different import mechanism) or mention when to use the 'activate' parameter. No explicit alternatives or exclusions are given.

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 provided, so description alone must convey behavioral traits. It mentions returning status, timing, and errors, which hints at the output, but doesn't clarify if results are sorted, paginated, or if recent means last N executions. Adequate but not detailed.

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, concise and to the point. Front-loaded with action and resource. Could be slightly more structured but no fluff.

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?

With 4 optional parameters, no output schema, and no annotations, the description is minimal. It covers basic purpose but lacks details on result format, pagination, default limit, or error handling. Adequate but incomplete.

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 coverage is 100%, so baseline is 3. Description adds no extra meaning beyond the schema's parameter descriptions. No additional guidance on default server behavior or usage.

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 clearly states 'List recent workflow executions on an n8n server' and mentions the data shown (status, timing, errors). It distinguishes from siblings like n8n_list_workflows but doesn't explicitly compare to similar list tools.

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?

No explicit usage guidelines or comparisons to alternatives. However, the description implies monitoring or debugging use cases. Lacks when-not-to-use or prerequisite info.

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, but the description is straightforward and implies a read-only operation. However, it does not disclose if the list is cached, if it requires authentication, or any rate limits. For a simple listing, this is adequate but not thorough.

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 sentence, no wasted words. It perfectly fits 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?

Given the tool has no parameters, no output schema, and simple functionality, the description is minimal but sufficient. However, it lacks explanation of the output format or structure (e.g., names, IDs), which could be inferred but is not explicit.

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 has no parameters, and schema description coverage is 100%. The description does not need to add parameter details. It correctly implies no input is required, so no additional semantics are necessary.

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 'list' and the resource 'n8n server connections', distinguishing it from sibling tools like n8n_list_workflows and n8n_ping_server. However, it does not explicitly differentiate from 'list executions' or other list tools, but the resource is distinct enough.

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 no guidance on when to use this tool versus alternatives. It does not explain prerequisites, such as needing an added server, or when to prefer this over n8n_ping_server for checking server status.

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 must disclose behavior. It confirms the operation is a read (listing), which is non-destructive, and mentions return fields. However, it does not specify if there is any filtering beyond the optional limit parameter, or if pagination is handled.

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 short (two sentences) and front-loaded with the main purpose. The first sentence clearly states the action, and the second adds useful detail about return values. Could be slightly more concise by combining, but still 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?

Given the tool has only 2 parameters with full schema coverage, no output schema, and no annotations, the description adequately conveys the basic function and return fields. It lacks details on error handling, permissions required, or whether the listing is paginated, but meets minimum viability for this simple tool.

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%, meaning both parameters are already described in the schema. The description does not add additional semantic meaning beyond what the schema provides (e.g., default server behavior, limit meaning). 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 specifies the verb 'list' and the resource 'workflows on an n8n server', and distinguishes from siblings by noting the return fields (names, IDs, active status, node counts), making its purpose clear and distinct.

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 usage for listing workflows, but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like n8n_get_workflow (single workflow) or n8n_list_executions. No exclusions or prerequisites are mentioned.

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 must fully disclose behavior. It reveals that it tests connectivity but does not specify what happens on success/failure, whether it is idempotent, or what side effects occur. Since the tool name includes 'ping', the behavior is somewhat implied, but more explicit disclosure is needed.

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, concise sentence that directly states the tool's purpose with no unnecessary words. It is front-loaded and 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?

Given the tool's simplicity (ping test, one optional parameter) and no output schema, the description is nearly sufficient. However, it lacks details on expected outcomes or prerequisite conditions (e.g., server must exist), which would improve 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 input schema has 100% coverage with a description for the only parameter ('server_name: 'Server name. Uses default if omitted.'). The tool description does not add further meaning, so 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 clearly states 'Test the connection to an n8n server', which specifies a verb ('test') and a resource ('connection to n8n server'). It distinguishes itself from sibling tools like n8n_add_server or n8n_list_servers, though it could be more specific about what 'connection' means (e.g., checking reachability or authentication).

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 no guidance on when to use this tool versus alternatives. It does not mention when not to use it or suggest other tools for related tasks. For example, there is no hint that n8n_add_server might be needed first.

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?

Without annotations, the description carries full burden. It does not disclose if removal is permanent, requires confirmation, or has side effects. No mention of permissions needed or behavior for non-existent server.

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?

Single sentence is concise and front-loaded. No wasted words. Could benefit from additional context but not at expense of brevity.

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 removal tool with one parameter, the description is too minimal. It lacks information on idempotency, error states, or relationship to sibling tools like n8n_add_server. Output schema is absent, but description should still hint at return value or confirmation.

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 coverage is 100% with one required parameter 'server_name' with clear description. The description adds the context that removal is from configuration, but parameter insight is already complete in 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?

The description 'Remove an n8n server from the configuration' clearly states the verb (remove) and resource (n8n server). However, it does not differentiate from sibling tools like n8n_delete_workflow, which is a different resource but similar verb. The description is clear but lacks specificity about the scope.

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?

No guidance on when to use this tool vs alternatives (e.g., n8n_list_servers to see available servers, n8n_ping_server to check status). The description does not mention prerequisites (e.g., server must exist) or consequences (e.g., irreversible removal).

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 full burden. It mentions 'Send the full updated workflow JSON' which hints at a full replacement behavior, but does not disclose whether partial updates are supported, what happens to existing workflow state (destroyed?), or authentication requirements. For a write operation, this is insufficient.

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 very concise: two sentences, no fluff. It front-loads the purpose and adds a key behavioral hint ('full updated'). However, it is slightly under-specified for a mutation tool, preventing a perfect score.

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 (mutation with 3 parameters) and lack of annotations/output schema, the description is too brief. It does not explain return values, partial updates, or error scenarios. The hint about 'full' is valuable but incomplete.

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 baseline is 3. The description adds no extra information beyond the schema's parameter descriptions. It mentions 'Send the full updated workflow JSON' which aligns with the workflow_json parameter but adds no new semantics.

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: 'Update an existing n8n workflow' with the verb 'Update' and the resource 'workflow'. It distinguishes from siblings like n8n_create_workflow and n8n_delete_workflow by specifying 'Update an existing', implying modification. However, it could be slightly more explicit about differentiating from n8n_export_workflow or n8n_import_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 description implies usage for updating workflows but does not explicitly state when to use this tool over alternatives (e.g., n8n_create_workflow for new workflows, n8n_delete_workflow for deletion). No guidance on prerequisites or when not to use it is provided.

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