Get Folder

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds value by specifying that the response includes the folder and its lists, but does not elaborate on any other behavioral traits like pagination or data volume.

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 a single, compact sentence that is front-loaded with the verb and resource. Every word earns its place, and there is no unnecessary verbosity.

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?

Given the tool's simplicity (one parameter) and comprehensive annotations, the description is somewhat complete. It states the primary output (Folder and Lists) but omits details about response structure or how to obtain the folder_id. For a read-by-id tool, this is acceptable but not fully complete.

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 only parameter folder_id has zero schema description coverage, and the tool description does not provide additional context about the parameter, such as how to obtain it or expected format. Since the description does not compensate for the schema gap, the parameter semantics are weak.

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 'Get a ClickUp Folder and its Lists' clearly identifies the verb (Get) and resource (Folder and its Lists), and implicitly distinguishes from sibling get_list by including Lists. However, it doesn't explicitly differentiate from get_workspace_hierarchy or search_workspace, so it falls short of a 5.

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 no guidance on when to use this tool versus alternatives like get_list or get_workspace_hierarchy. There is no mention of prerequisites, typical use cases, or when to avoid it.

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