Generate n8n Security Audit

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

Annotations indicate readOnlyHint=false and idempotentHint=false, but the description only says 'Checks for...' which sounds read-only, and does not disclose any potential side effects, report output format, or operational requirements. The description adds little beyond the annotations, and the lack of detail about mutation risk is notable.

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 structured with an Args list. However, the 'etc.' is filler and the prose is slightly redundant with the schema, but it remains easily scannable and appropriately sized for a simple tool.

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?

The tool has no output schema, yet the description does not explain what the audit report contains or how it is returned (e.g., as a response project, file, or console output). It also omits behavior when categories are omitted (though the schema covers this). The description lacks sufficient context for an agent to invoke the tool and interpret the result robustly.

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 descriptions for both parameters, and the description's Args section mostly duplicates the schema (including enum values and default). It provides no additional semantics, examples, or parameter interactions, so a 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 generates a security audit report for the n8n instance, listing specific check areas (security misconfigurations, abandoned workflows, credential exposure). This specific verb+resource distinguishes it from sibling CRUD tools like n8n_list_workflows or n8n_delete_execution.

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 purpose implies it is used for security audits, but there is no explicit when-to-use guidance or mention of alternatives. The sibling context makes the usage fairly clear, but the description itself lacks direct exclusions or comparative guidance.

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