nexus_create_tag

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

Annotations already communicate that this is a non-read-only, non-idempotent, non-destructive action. The description adds a useful permission caveat and describes the success/error return shape. However, it does not disclose broader side effects, such as whether the tag becomes immediately visible or how duplicates are handled, which would be valuable given openWorldHint.

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 short and front-loaded with the core action, then follows with a concise return-value note. It contains no filler or redundant restating of the schema.

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 create operation, the description and schema together provide enough information: required name, optional attributes, permission caveat, and return shape. Minor gaps remain around usage guidance versus related tag tools and more precise permission requirements, but these are not severe enough to impede correct invocation.

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 input schema already documents all five parameters with clear descriptions, so schema coverage is 100%. The tool description adds no additional parameter-level meaning, which fits the baseline of 3 for high schema coverage.

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 states a clear action, 'Create a new tag,' on a specific resource, and identifies it as the v2 GraphQL operation. This clearly distinguishes it from sibling tools like nexus_update_tag and nexus_discard_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 word 'new' clearly signals this is for creating tags, not updating or discarding existing ones. It also provides a relevant precondition by noting moderator permissions may be required. It does not explicitly name alternatives, but the purpose is specific enough to guide selection.

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