superset_tag_create

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

With no annotations provided, the description carries the full burden and does so excellently. It discloses the API returns {} without a tag ID, the workaround of calling superset_tag_list, and the broken direct attachment endpoints. These are significant behavioral quirks beyond what schemas convey.

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 an 'IMPORTANT' callout, a clear behavioral note, and an Args section. Every sentence provides essential information without fluff, making it appropriately sized 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?

Given the tool has no annotations and a sparse schema, the description is remarkably complete. It covers creation behavior, attachment process, return quirks, and parameter formats. While it doesn't mention permissions or duplicates, the provided context is sufficient for an agent to invoke the tool correctly.

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 schema provides only parameter names and types with zero descriptions. The description adds rich meaning for each parameter, especially objects_to_tag with its JSON format, element pairs, and allowed object types. This fully compensates for the schema's lack of semantics.

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 new tag and optionally attach it to Superset objects,' which is a specific verb and resource. It distinguishes from sibling tools like superset_tag_list, superset_tag_update, and superset_tag_delete by focusing on creation.

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 provides explicit usage guidance: it mentions that object attachment is only possible during creation, warns that direct attachment endpoints do not work in 6.0.1, and instructs to call superset_tag_list to obtain the new tag's ID. This effectively tells when to use this tool and what alternatives to use.

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