Server Quality Checklist

Tool Scores

• get_execution_statusA
  3.5/5.0
  Behavior2/5

  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.

  Conciseness5/5

  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.

  Completeness3/5

  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.

  Parameters3/5

  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.

  Purpose5/5

  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.

  Usage Guidelines3/5

  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.

• execute_workflowA
  4/5.0
  Behavior4/5

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

  The description goes beyond the annotations by disclosing at-least-once delivery semantics and explicitly warning against blind retries on timeout or network errors. This is valuable behavioral context that the annotations (idempotentHint=false, destructiveHint=true) do not fully convey. It does not contradict the annotations.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences, with no redundant words. The first sentence states the purpose, and the second adds a critical operational warning. It is front-loaded and every word earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The description covers the core purpose and the most important behavioral caveat, but it omits details about the return value or how the workflow's execution status can be tracked afterward. Given the lack of an output schema and the existence of a get_execution_status sibling, this gap makes the tool somewhat incomplete for an agent to use confidently.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters2/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  With 0% schema description coverage, the description was expected to compensate by explaining the parameters. It mentions 'supplied JSON input' but gives no detail about the structure or content requirements, and it does not describe workflowId beyond what the schema already shows. This leaves the agent with very little semantic guidance.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the action ('Executes a tagged n8n workflow') and the method ('through its webhook using the supplied JSON input'). It straightforwardly distinguishes this from sibling tools like list_workflows and get_execution_status by focusing on execution rather than listing or status retrieval.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description makes it clear that this tool runs a workflow, which implicitly signals when to use it compared to the read-only sibling tools. However, it does not explicitly state 'use this when you need to trigger a workflow' or mention any exclusions or alternatives, so it falls short of a 5.

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

• get_workflow_schemaA
  4.2/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the burden. It discloses that the tool returns schema and webhook details, which is a specific behavioral trait beyond a generic 'get'. It does not mention error cases or side effects, but for a simple getter this is adequate.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, focused sentence with no fluff. It conveys the core purpose and key return contents efficiently.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (one parameter, no output schema, no annotations), the description is mostly complete. It explains what the tool returns and implies its role in workflow execution. It could mention error behavior or read-only nature, but the low complexity lowers the bar.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema has 0% description coverage, and the only parameter is workflowId. The description mentions 'given n8n workflow', which clarifies that workflowId refers to a workflow identifier but adds no format or usage details. The parameter name is self-explanatory, but the description doesn't fully compensate for the lack of schema description.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description states a specific verb ('Returns') and a specific resource ('input schema and webhook details needed to call a given n8n workflow'), clearly distinguishing this from sibling tools like execute_workflow or list_workflows. It answers 'what does it do?' precisely.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage context: it is needed before calling a workflow, as it provides the schema and webhook details required for that call. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to infer when to use it.

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

• list_workflowsA
  4.2/5.0
  Behavior3/5

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

  No annotations are provided, so the description must carry the burden. It discloses the filtering mechanism (MCP tag) and governance boundary, which is useful. However, it does not explicitly state whether the operation is read-only, describe return format, or mention pagination/rate limits. For a list operation, this is acceptable but not comprehensive.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is only two sentences, direct and front-loaded with the action. Every word contributes, explaining both what it does and why the tag matters. No redundancy or unnecessary detail.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's simplicity (no parameters, no output schema), the description provides adequate context: it names the resource, the filtering criteria, and the governance significance. It could add details about return values or pagination, but for a list tool, the description is fairly complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool has 0 parameters, and the input schema is empty. The baseline for 0 params is 4. The description does not need to explain parameter semantics, but also adds no extra parameter context. Since there are no parameters to clarify, this score is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's function: 'Lists n8n workflows opted in through the configured MCP tag.' It uses a specific verb (lists) and resource (n8n workflows) and adds scope via the tag, distinguishing it from siblings like execute_workflow or get_execution_status.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies when to use this tool—to discover workflows the agent may call, governed by the MCP tag. It provides context about the governance boundary but does not explicitly mention alternatives or when not to use it. This is clear context without exclusions, so a 4.

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