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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds only the REST endpoint mapping and says nothing about pagination, result ordering, whether nested lists are returned, or archived-item behavior beyond what the schema already documents.

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 short sentences, front-loaded with the action and scope; nothing is padded. The second sentence is mildly redundant with the first but adds the REST mapping, which is genuinely useful for an agent reasoning about ClickUp's API.

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 read-only list tool with full schema coverage and readOnlyHint annotations, the definition is minimally viable. It omits pagination/truncation behavior and any hint about what is returned, which matter because no output schema exists.

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%, so both parameters (space_id, archived) are already documented in the schema; baseline 3 applies. The REST path does reinforce that space_id is a path parameter, but no additional semantics or format details are contributed.

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?

States a specific verb and resource ("List folders") and scopes it to a space, plus the underlying REST call GET /space/{space_id}/folder. It does not explicitly distinguish itself from hierarchy-adjacent siblings like clickup_list_folderless_lists or clickup_list_lists, but the noun alone is specific enough to pick the right tool.

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?

There is no when-to-use guidance, no prerequisites (e.g., needing a space_id obtained from clickup_list_spaces), and no mention of alternatives for enumerating containers. Usage is only implied by the tool name and the REST path.

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