n8n_get_tag

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, the description doesn't confirm this, nor does it disclose error behavior (e.g., what happens if the tag_id doesn't exist), rate limits, or whether the returned details include metadata like creation date or associated workflows.

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 appropriately brief for a simple retrieval operation, but the structure is poor due to the '[UNIFIED]' prefix which appears to be internal metadata rather than helpful context for the agent.

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 lack of annotations, output schema, and parameter descriptions, the description is insufficient. It should explain the 'site' parameter and provide basic context about what constitutes a 'tag' in n8n (workflow categorization tags), but provides neither.

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?

With 0% schema description coverage, the description must compensate for both parameters. It only implicitly covers tag_id by mentioning 'by ID', but completely fails to explain the 'site' parameter (which n8n instance to query), leaving a critical parameter undocumented.

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 verb (Get), resource (tag details), and lookup method (by ID), which effectively distinguishes it from sibling operations like n8n_list_tags, n8n_create_tag, or n8n_delete_tag. However, the '[UNIFIED]' prefix is metadata noise that doesn't aid understanding, and it doesn't specify that these are n8n workflow tags.

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 usage guidance is provided. There is no indication of when to use this tool versus n8n_list_tags (for searching) or n8n_get_workflow_tags (for getting tags associated with a workflow), nor any prerequisites like needing the tag ID beforehand.

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