clickup_list_list

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

No annotations provided, so description carries full burden. Discloses return format ('compact array of list objects (id, name, task_count, archived)') and the mutual exclusivity constraint. Could mention any authentication requirements or rate limits, but is sufficient for a read operation.

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 sentences, no wasted words. First sentence states purpose and constraint, second sentence describes return value and provides alternative tool. Front-loaded with essential 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?

Given simple parameters, no output schema, and no annotations, the description covers all necessary aspects: what it does, required parameters, return structure, and relation to sibling tools. Complete for an AI agent to select and invoke 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?

Schema coverage is 100%, but description adds value by clarifying that space_id returns folderless lists and reinforcing the mutual exclusivity. The description also explains how to obtain folder_id/space_id from other tools (clickup_folder_list, clickup_space_list), which the schema does not.

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?

Clearly states 'List ClickUp lists under either a folder or a space (folderless lists)'. Specifies verb, resource, and context. Distinguishes from sibling clickup_task_list by indicating when to drill into a specific list.

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?

Explicitly states that exactly one of folder_id or space_id must be provided. Provides alternative tool (clickup_task_list) for drilling into a specific list, offering clear when-to-use and when-not-to-use guidance.

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