n8n-patterns-categories

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

The description indicates a read-only 'list' operation with no side effects. While no annotations exist, the description accurately conveys the tool's non-destructive nature. It does not provide additional behavioral details (e.g., pagination, format), but for a simple list with no parameters, this is transparent enough.

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 extremely concise at 4 words plus a parenthetical count. It is front-loaded with the action and resource, leaving no redundant text. Every word is informative.

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 parameters, no output schema, low complexity), the description provides the essential information: it lists all categories and specifies the total count. However, it lacks details about the output structure (e.g., fields returned), which would be helpful for an agent to parse results.

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?

There are no parameters in the input schema, and the description does not need to add parameter information. The schema coverage is 100% (empty), so the baseline score of 4 applies.

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 a specific verb 'List' and resource 'workflow categories', clearly stating the action and scope. It distinguishes this tool from siblings (e.g., list-credentials, n8n-patterns-get) by specifying it returns all categories, and even gives the exact count (16 total).

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 when-to-use or when-not-to-use instructions are provided. The description implies it's for retrieving all workflow categories, but does not mention alternatives or context for selecting this tool over similar list tools or pattern-specific tools.

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