createTag

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

Beyond annotations, the description discloses that added_by is wrapper-managed (hardcoded to 0), that duplicate tag_name within a group is silently accepted (no uniqueness constraint), and that group_tag_id FK is not enforced, leading to orphan tags. These critical behavioral details aid agent decision-making.

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 well-structured with clear sections (Use when, Required, behavioral notes, parameter interactions, See also, Returns). It is front-loaded with purpose. While somewhat lengthy, each section adds value and is justified for the tool's complexity.

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?

The description covers purpose, inputs, required fields, side effects (duplicates, orphan risks), return format (status and created record with ID), and references sibling tools. It fully addresses the complexities of the tool despite lacking an output schema.

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?

The description adds meaning: tag_name is 'the visible label', group_tag_id is 'tag group from listTagGroups'. It also clarifies that added_by is not an input. With 50% schema description coverage, the description compensates slightly, but tag_name's schema lacks description entirely, and the description provides basic meaning.

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 'Create a tag - Create a new tag record' and 'Writes live data.' It distinguishes itself from sibling tools like createTagGroup and createTagRelationship by focusing solely on creating a tag record.

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?

It explicitly says 'Use when: adding a new tag' and mandates that the group_tag_id must exist, discoverable via listTagGroups. It provides a recommended pre-check pattern to avoid duplicates and references updateTag for modifications, offering clear when-to-use and when-not-to-use guidance.

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