workspaces_list

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

With no annotations provided, the description carries the full burden of disclosing behavior. It indicates a read-only operation through 'Get' and 'Returns', and adds context about the authenticated user. However, it does not explicitly state that it is non-mutating, describe potential pagination, or clarify the scope of 'metadata', leaving some behavioral aspects undisclosed.

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 two sentences, immediately states the core action, and includes the essential return information with minimal waste. It is well-structureured and front-loaded, earning a perfect score.

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 covers the purpose, scope, and return values. There are no complex configurations or hidden behaviors, so the description is complete enough for an agent to select and invoke this tool correctly.

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 input schema has zero parameters, so the baseline is 4. The description adds meaningful context by saying 'all' and 'accessible to the authenticated user', which clarifies the implicit filter. No parameter details are needed beyond what the schema already shows.

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 lists all ClickUp workspaces for the authenticated user, with a specific verb ('Get a list') and resource ('workspaces'). It also mentions the returned data (IDs, names, metadata), and distinguishes itself from sibling tools like workspaces_seats_get by focusing on workspaces generally.

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 usage when a user needs to retrieve all accessible workspaces, but it does not explicitly state when to use this tool versus alternatives such as workspaces_seats_get. No exclusions or alternative comparisons are mentioned, leaving the context clear but the guidance implicit.

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