Security audit

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the action of generating a report. It does not mention side effects, performance implications, permissions required, or what happens if categories are omitted. The schema already describes default behavior for categories.

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 short and to the point, with one sentence and a list of categories. No fluff or repetition. It could benefit from additional context, but for its length it is 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 (no required parameters, two optional params fully described in schema), the description is minimally adequate. It explains the purpose and categories. However, it omits details about the output format (even though output schema exists) and any prerequisites or contextual setup needed for the audit to be useful.

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%: both parameters have descriptions. The tool description lists the categories but adds no semantic value beyond what the schema already provides (e.g., meaning of each category, format of daysAbandonedWorkflow). Baseline 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 the tool generates a security audit report for the n8n instance and lists the possible categories. This verb+resource combination is distinct from all sibling tools, which are CRUD operations or execution/health checks.

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 does not provide explicit guidance on when to use this tool versus alternatives. While it is implicitly for security audits, no context is given about prerequisites, frequency, or exclusions. The sibling list contains no other audit tools, so differentiation is inherent but not articulated.

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