n8n_create_tag

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 only states that a tag is created, but omits side effects, uniqueness constraints, error behavior, permissions, or return value. This is a significant gap for a mutation tool.

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 a single, focused sentence with no filler or redundancy. It conveys the essential purpose immediately and does not waste any tokens.

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?

For a simple create operation with one parameter this is minimally usable, but the lack of annotations and output schema means the description should provide more context about expected behavior, such as whether duplicate names are rejected or what response to expect. The current description leaves too much unknown.

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% and the single parameter 'name' already has a description ('Tag name') in the schema. The tool description does not add meaningful parameter detail beyond what the schema provides, so the baseline score of 3 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 ('Create'), names the resource ('a new tag'), and adds context ('for organizing workflows'). It clearly distinguishes itself from sibling tag tools like n8n_list_tags, n8n_update_tag, or n8n_delete_tag because it states the action is creation of a brand-new tag.

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 any guidance on when to use this tool versus alternatives. While the intent to create a tag is clear, there is no mention of when not to use it, whether to reuse existing tags, or any relationship to tools like n8n_update_tag or n8n_list_tags.

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