clickup_user_get

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

No annotations are provided, so the description must convey behavioral traits. It states 'Returns the user object' but does not disclose error behavior, permissions, or whether the operation is read-only. The description is adequate but lacks depth given the absence of annotations.

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 concise sentences that front-load the purpose and then provide usage guidance. Every sentence adds value; no fluff or redundancy.

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 a simple fetch operation. The description lists returned fields (username, email, color, profile picture, role) and identifies siblings. With no output schema, the description provides a reasonable overview, though it could be slightly more detailed on error conditions.

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%: both team_id and user_id have clear descriptions in the input schema. The description adds minimal additional meaning beyond the schema, so baseline 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?

Clear verb and specific resource: 'Fetch the profile of a specific member of a ClickUp workspace.' It lists fields like username, email, color, profile picture, role. Explicitly distinguishes from siblings: clickup_member_list for task/list members and clickup_whoami for the authenticated user.

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?

Explicit when-to-use and when-not-to-use: 'Use clickup_member_list for task/list members; use clickup_whoami for the authenticated user.' This directly guides the AI agent on selecting the correct tool and avoiding misuse.

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