n8n-mcp

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 states the tool generates a security audit but doesn't describe what this entails operationally - whether it's a read-only scan, if it requires specific permissions, if it's resource-intensive, what the output format is, or any side effects. The mention of 'days_abandoned_workflow' in the schema suggests workflow-related auditing, but this isn't explained in the description.

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 brief and front-loaded with the core purpose. The single sentence efficiently communicates the main function followed by category examples. However, the category listing could be more structured, and the lack of parameter guidance means it's somewhat under-specified rather than optimally concise.

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 that there's an output schema (which should document return values) and only 2 parameters, the description provides a basic but incomplete picture. It covers the core purpose adequately but fails to explain parameter usage, behavioral characteristics, or how this tool fits into the broader security audit workflow. For a tool that presumably produces important security information, more context would be 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 has 0% description coverage, so the description must compensate. It mentions 'Categories: credentials, database, nodes, filesystem, instance' which partially explains the 'categories' parameter, but doesn't clarify if this is an exhaustive list, if multiple can be selected, or their meaning. It completely ignores the 'days_abandoned_workflow' parameter, leaving its purpose and relationship to the audit unexplained.

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: 'Generate a security audit' with specific categories listed (credentials, database, nodes, filesystem, instance). This provides a specific verb ('generate') and resource ('security audit') with scope details. However, it doesn't explicitly distinguish this tool from potential audit-related siblings, though none appear in the sibling list.

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. While it lists categories, it doesn't indicate whether these are required, optional, or exhaustive, nor does it mention prerequisites, dependencies, or when this audit generation might be preferred over other security or monitoring tools in the system.

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