clickup_tag_create

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: it's a creation operation (implies mutation), returns an empty object on success, and warns about API parameter naming inconsistencies with the update tool. It doesn't mention authentication requirements or rate limits, but covers the essential behavioral context.

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 efficiently structured in three sentences, each earning its place: purpose and scope, prerequisite relationship, and behavioral notes about API inconsistency and return value. No wasted words, front-loaded with the core purpose.

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 mutation tool with no annotations and no output schema, the description provides good contextual completeness: it explains the creation purpose, scope, prerequisite relationship, API inconsistency warning, and return behavior. It could mention authentication requirements but covers the essential context given the tool's complexity.

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?

Schema description coverage is 100%, so the schema already fully documents all 4 parameters. The description adds minimal parameter semantics beyond the schema - it mentions the API inconsistency between create/update parameter names but doesn't provide additional meaning about the parameters themselves. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Define a new tag') and resource ('in a ClickUp space'), distinguishing it from sibling tools like clickup_tag_list (list) and clickup_tag_update (update). It explicitly mentions the scope ('space-scoped') and the prerequisite relationship with clickup_task_add_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 description provides explicit guidance on when to use this tool ('must be created before they can be applied to tasks via clickup_task_add_tag') and mentions an alternative for viewing results ('use clickup_tag_list to see the created tag'). It also warns about API inconsistencies with clickup_tag_update.

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