clickup_group_update

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

Discloses atomicity and return value ('Returns the updated group object'). However, with no annotations, it doesn't cover permissions, side effects, or error conditions, leaving some behavioral traits unclear.

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?

Two sentences, front-loaded with purpose, no unnecessary words. Every sentence earns its place.

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 simple mutation tool with good parameter descriptions, the description covers purpose, usage, and return value. Lacks examples or error info, but sufficient for a straightforward tool.

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%, but the description adds value: explains that add_members is additive, rem_members is no-op if not a member, and name can be omitted to keep current name. This goes 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 the tool's purpose: 'Rename a user group and/or add/remove its members.' This specifies the verb (rename, add/remove) and the resource (user group), distinguishing it from siblings like create, delete, and list.

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?

Provides clear guidance: 'Use clickup_group_list first to see current membership' and 'All changes are applied in one call.' This helps the agent understand preconditions and atomicity, but lacks explicit when-not-to-use or comparison to alternatives.

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