clickup_member_list

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

With no annotations, the description carries the burden. It discloses output format (array of user objects with fields) and the parameter constraint. However, it does not describe permissions required, rate limits, or any side effects, leaving some behavioral aspects ambiguous.

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: first states purpose and constraint, second covers return format and related tools. No redundant information. Front-loaded with essential details.

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 no output schema, the description explains return type and fields. Cross-references to sibling tools for related actions. Lacks mention of pagination or error scenarios, but overall sufficient for a straightforward list operation.

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% with detailed descriptions. The description adds value by reinforcing the mutual exclusivity of list_id and task_id and specifying that exactly one must be provided, which is not enforced in the schema (required empty).

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 it lists members (users with direct access) of a task or list, using specific verbs and resources. It differentiates from sibling tools by mentioning addition of workspace members (clickup_user_invite) and guest sharing (clickup_guest_share_task/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 context on when to use (list members) and directs to alternative tools for adding users. Mentions the 'exactly one' constraint. Lacks explicit 'do not use when' conditions but provides sufficient guidance for correct selection.

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