clickup_folder_get

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

Since no annotations are provided, the description carries the burden. It discloses that task_count is a string 'per API', which is a notable behavioral detail not in the schema. It also clarifies that it returns the folder object with child lists. However, it does not explicitly state that the operation is read-only or mention any authentication requirements.

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, front-loading the key purpose and return details, and includes a concise alternative usage. Every sentence adds value, with no redundancy or fluff.

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 one-parameter tool without an output schema, the description adequately explains what the tool returns and provides an alternative for a related task. It could be slightly improved by noting that it returns a single folder object with nested lists, but overall it is clear and sufficient for the complexity level.

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% with a clear description for folder_id. The tool description does not add further meaning to the parameter beyond what the schema already provides (ID of the folder to fetch). The mention of 'Obtain from clickup_folder_list' is already in the schema. Hence, no extra value is added for the parameter.

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 verb 'Fetch' and the resource 'full object for a single ClickUp folder' and enumerates specific fields (name, task_count, archived status, child lists). It distinguishes itself from siblings like clickup_folder_list (which lists folders) and clickup_list_list (which lists lists).

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 directly provides an alternative tool usage: 'Use clickup_list_list with folder_id to get just the lists.' This instructs the agent when to choose a different tool. However, it does not explicitly state when not to use this tool or broader context like whether it works for archived folders.

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