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

Annotations already declare readOnlyHint=true, and the description confirms a read operation with 'Get'. It adds valuable context about the ClickUp API token and the specific REST endpoint (GET /user), enhancing understanding of authentication and scope beyond the annotation hint.

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 consists of two short, front-loaded sentences with no filler. It states the main action first and includes the REST endpoint for reference, effectively using every word.

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, parameterless tool with no output schema, the description sufficiently explains what it does and its authorization context. No additional return-value details are necessary for this resource type.

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?

The tool has zero parameters, and the schema confirms no required inputs. With 100% schema coverage and no parameters to describe, the baseline of 4 for zero-parameter tools applies appropriately.

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 'Get the user associated with the current ClickUp API token' with a specific verb (Get), resource (user), and scope (current token). This distinguishes it from sibling tools focused on tasks, lists, spaces, etc.

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 provides clear context by mentioning the token association and the REST endpoint, making the usage obvious. While it doesn't explicitly list alternatives or exclusions, the tool's unique resource scope among siblings makes the intended use clear.

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