clickup_tag_update

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

With no annotations, the description fully discloses behavior: 'All tasks using the tag are automatically updated with the new name/colours' and 'Returns an empty object on success'. This provides complete transparency about side effects and return value.

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 concise (three sentences) and front-loaded: first sentence states purpose, second explains behavior, third adds critical API note. Every sentence adds value, with no wasted words.

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 tool is simple (updating a tag) and the description covers purpose, behavior, return value, and an important inconsistency note. No output schema exists, but the description adequately specifies the return. All necessary context is provided.

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 coverage is 100%, so the schema already documents all parameters. The description adds value by highlighting the API inconsistency (fg_color/bg_color vs tag_fg/tag_bg) which helps agents use the correct parameter names. However, it does not elaborate on parameter meanings beyond the schema.

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 'Rename a tag or change its colours within a ClickUp space', specifying the verb (rename/change) and resource (tag). It distinguishes from sibling tools like clickup_tag_create, clickup_tag_delete, and clickup_tag_list by noting the API inconsistency, making the tool's purpose unambiguous.

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 tells when to use this tool (to update tag name/colors) and provides a crucial note about the API inconsistency between tag_update and tag_create. It implicitly differentiates from sibling tools (create, delete, list) but could be more explicit about when not to use this tool (e.g., for creating new tags).

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