superset_tag_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a POST request to create a tag, implying a write operation, but lacks details on permissions required, error conditions, rate limits, or whether the operation is idempotent. The description adds minimal context beyond the basic action, leaving significant behavioral aspects undocumented.

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 and appropriately sized, with a clear purpose statement, endpoint details, and separate sections for arguments and returns. It avoids unnecessary fluff, though the endpoint detail could be considered slightly technical. Every sentence adds value, making it efficient and easy to parse.

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's complexity (a simple create operation with one parameter) and the absence of annotations and output schema, the description is moderately complete. It covers the purpose, parameter semantics, and return type, but lacks behavioral details like error handling or permissions. For a mutation tool with no structured support, it meets minimum viability but has clear gaps in guidance and transparency.

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 includes an 'Args' section that explains the 'name' parameter as 'Name for the tag', adding semantic meaning beyond the schema, which has 0% description coverage and only provides a title. This compensates well for the low schema coverage, though it does not detail constraints like length or allowed characters. With only one parameter, this is sufficient for clarity.

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 specific action ('Create a new tag in Superset') and identifies the resource ('tag'), distinguishing it from sibling tools like superset_tag_delete, superset_tag_get_by_id, and superset_tag_list. It explicitly mentions the POST endpoint and the purpose of tagging objects like charts and dashboards, providing a complete and specific purpose statement.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., authentication), compare it to sibling tools like superset_tag_list or superset_tag_delete, or specify scenarios where tag creation is appropriate. Usage is implied only by the action of creating a tag, with no explicit context or exclusions provided.

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