clickup_member_list

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

With no annotations, the description carries full burden. It discloses the return format ('array of user objects with id, username, email, color'), which is valuable behavioral context. However, it doesn't mention permissions needed, rate limits, or pagination behavior, leaving some gaps.

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?

Three sentences, each earning its place: first states purpose, second specifies parameter constraint, third provides usage alternatives. No wasted words, front-loaded with core functionality.

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 read-only list tool with no annotations and no output schema, the description is reasonably complete: it explains purpose, parameter rules, return format, and alternatives. Missing details like pagination or error handling keep it from a perfect score, but it covers the essentials well.

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 documents both parameters thoroughly. The description adds minimal value by restating the mutual exclusivity rule and implying the parameters' purpose, but doesn't provide additional syntax or format details 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 action ('List members') and resource ('users with direct access of a specific task or list'), distinguishing it from siblings like clickup_user_invite (add users) or clickup_guest_share_task/list (add guests). It specifies the scope as direct-access users, not guests.

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?

Explicitly states when to use alternatives: 'Use clickup_user_invite to add people to the workspace first; use clickup_guest_share_task/list to add guests.' Also clarifies the mutual exclusivity of task_id and list_id, though this is also in the schema.

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