clickup_space_list

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

With no annotations, the description carries the full burden. It discloses that the tool returns a compact array with specific fields (id, name, private, archived) and describes the archived parameter's effect. No mention of rate limits or authentication, but the operation is clearly a read-only list. No contradictions.

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: first states purpose, second adds context about hierarchy, third provides return type and drill-down guidance. No wasted words, front-loaded with key information.

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?

No output schema exists, so description explains return shape. Both parameters are well-documented with usage hints. Sibling tools for drilling down are referenced. Complete for a list tool with simple configuration.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond schema: for team_id, it explains the omission behavior using a config default; for archived, it clarifies true/false/omit. This provides actionable context.

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 'List all spaces in a ClickUp workspace' after the tool name, defining the verb (list) and resource (spaces). It also distinguishes from siblings by naming clickup_folder_list and clickup_list_list as tools to drill down.

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 explicitly provides usage guidance: 'Use clickup_folder_list or clickup_list_list with a space_id to drill down.' It tells the agent when to use this tool and when to use alternatives, and explains the compact return format.

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