get_members

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Get members') and target scopes, but does not mention that one of the IDs is likely required, whether the operation is read-only, what happens if multiple IDs are supplied, or any return characteristics. The verb 'Get' implies read-only, but key behavioral details are missing.

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 a single, concise sentence: 'Get members of a ClickUp space, folder, or list.' It contains no fluff, gets straight to the point, and is appropriately sized for the tool's simplicity.

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 description is minimal but the tool itself appears simple. However, key context is missing: there is no output schema, and the description does not clarify that exactly one of the three IDs should be provided or how to choose among them. Given the simple nature and high schema coverage, it is minimally viable but leaves room for ambiguity.

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% (each parameter has a short description like 'List ID (optional)'), which meets the high-coverage baseline of 3. The tool description adds no additional meaning beyond the schema, such as mutual exclusivity of the IDs or that at least one is expected. The descriptions are minimal but present, so a baseline score of 3 is appropriate.

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 function: 'Get members of a ClickUp space, folder, or list.' It uses a specific verb ('Get') and resource ('members') with explicit scopes (space, folder, list), which differentiates it from sibling tools like get_team_members and get_guests. However, it does not explicitly name alternatives, so sibling differentiation is implicit rather than explicit.

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 implies when to use the tool: when you need members of a ClickUp space, folder, or list. It does not provide explicit guidance about when NOT to use it or mention alternative tools such as get_team_members. The usage context is clear enough but without exclusions or alternatives, it stops at 'implied usage.'

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