n8n_create_tag

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

No annotations provided, so description carries full burden. Fails to disclose: return value format (tag ID? object?), idempotency behavior (what if tag exists?), or required permissions. Only states basic creation intent.

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?

Extremely brief single sentence. Front-loaded with action verb. While efficient, the extreme brevity contributes to information gaps in other dimensions. '[UNIFIED]' prefix wastes 9 characters without adding value.

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?

No output schema exists, yet description omits what the tool returns (e.g., created tag ID). Missing error scenarios, parameter validation rules, or relationship to n8n_projects (implied by 'site' param). Incomplete for a resource creation tool.

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 has 0% description coverage with two required parameters ('site' and 'name'). Description implies 'name' is the tag name but provides no details on 'site' (n8n instance? project?), format constraints, or examples. Inadequate compensation for schema gaps.

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?

States specific verb (Create) and resource (tag) with context (workflow organization). The '[UNIFIED]' prefix is noise but harmless. Distinguishes from delete/update siblings by action, though could clarify difference from set_workflow_tags (which assigns tags vs creating them).

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 guidance on when to use versus alternatives like n8n_set_workflow_tags or n8n_update_tag. No mention of prerequisites (e.g., whether tag names must be unique) or error conditions.

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